fusionjs VS babili

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 don't need to worry about BS related to intermediate compilation bugs, NPM publishing interface, etc.

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.

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.

At work we use another framework called Fusion.js. One thing that we find important is its plugin system, which allows colocating server/client/hydration logic by concerns, rather than by environment, meaning we could enable/disable, e.g. Redux hydration by registering a plugin, rather than peppering redux code in a bunch of disparate lifecycle hooks.

The key is that the scoping happens for each iteration, not around the entire loop. That detail is nonobvious, given how many other languages have gotten it wrong, but I wouldn’t say it’s wild.

(If you’re curious how Babel deals with the more complicated cases of continue, break, labelled break, and return, try it out at https://babeljs.io/repl.)

I used https://babeljs.io/repl to know the size after the code has been transpiled.

You must have a basic understanding of JavaScript and be familiar with some of the features of ES6, the most recent version of JavaScript, to follow this tutorial. More information is available here if you’re unfamiliar with ES6. If you are more familiar with the older version of JavaScript, you might find the babel REPL more helpful to see how ES6 code is translated.

The JSX code is far easy to understand, but React, ReactDOM, or browser does not understand it. Babel comes into picture to translate JSX code to equivalent React code.

If we copy and paste the code in a Babel repl editor, we will get the equivalent React elements that we used earlier:

In your node project, add Babel and Webpack. They can “transpile “ your JSX code to browser compatible code. You can try it out here

If your project uses a bundler like webpack or rollup, then you can use the nullish coalescing operator in your code. But if you are using a browser, then you should use a transpiler like babel to transpile your code to ES5. You can use babel repl to transpile your code.

The Babel REPL is an easy way to see what the transpiled output looks like.

babel has an online playground