b) Don't do intermediate builds at all. This is what we do for monorepo-internal packages at Uber. Basically, our framework lets you specify what parts of node_modules should be transpiled when compiling the service. So basically you just have a single compilation step and the performance cost is alleviated by leveraging babel cache. The upside of this approach is you only need one file watching daemon and you... Source: over 2 years ago
I also worked on another framework which does ship with polyfills, but this one is very much a "we-call-you" framework, in the sense that it has an full-fledged, opinionated compiler with hundreds of hours worth of time spent on optimizations, and the inclusion of polyfills is also very much a deliberate choice made in the name of productivity. Source: over 2 years ago
We've gone down this rabbit hole with Fusion.js. The TL;DR: is core.js aims to be standard-compliant, which means it'll often pull in a lot of code to deal with obscure corner cases like dealing w/ Symbols. Source: almost 3 years ago
Do you know an article comparing Fusion.js to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Fusion.js. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.