proposal-nullish-coalescing VS babel-sublime

For more info about this feature, you can refer to the original proposal.

Propuesta

For comparison, here are the Javascript RFCs for the equivalent operators:

https://github.com/TC39/proposal-optional-chaining

https://github.com/tc39/proposal-nullish-coalescing

IMO optional chaining is a lifesaver when dealing with deeply nested JSON, and it's become indispensable in our Typescript code. But we also deal with JSON from various third-party endpoints in Python, and far too often we resort to an inefficient deep_get utility to make our code sensical.

> if json?.get("foo")?.get("bar")?[0]?.get("baz")

may seem messy but would be infinitely better than the fragile (note the nested list-of-a-single-dict, and how bugs can appear if it's not there):

> if json.get("foo", {}).get("bar", [{}])[0].get("baz")

or the inefficient

> if deep_get(json, "foo.bar.0.baz")

It's not nearly as good as the Typescript json.foo?.bar?.[0]?.baz - but it's good enough!

The nullish coalescing proposal provides a way to handle undefined or null values and provide default values for the expression. You can use the “??” operator to provide a default value for an expression.

GitHub | Website

Some of the most popular JavaScript linting tools are ESLint, JSHint, JSLint and JSCS. We're going to be using ESLint. It’s very flexible, easy to use and has the best ES6 support, which will be helpful if we introduce more modern JavaScript (that will be transpiled for older browsers using https://babeljs.io/). All rules for ESLint can be found here: https://eslint.org/docs/rules/.

This simply extends the existing build process that many front-end frameworks have. After Babel's done with its transpilation, it merely executes code to compile your initial screen into static HTML and CSS. This isn't entirely dissimilar from how SSR hydrates your initial screen, but it's done at compile-time, not at request time.

First, we switched the default compiler for new projects from Babel to SWC (Speedy Web Compiler). SWC is dramatically faster than Babel and requires zero configuration. We’ll continue to support Babel in any project currently using it.

Nuxt.js is an open-source JavaScript framework built on Vue.js, Node.js, Vite, and Babel.js used for creating fast, cutting-edge applications. Nuxt.js possesses similar features to Next.js, with the major difference being the web framework it is compatible with. Next.js is a React framework whereas Nuxt.js is a Vue framework.

Disclaimer: If you've already developed Babel or ESLint plugins, this article may not be as beneficial for you, as you're likely already familiar with the majority of the content covered here.

Preprocessors: SSGs leverage preprocessors to streamline the development process. Preprocessors like SASS for CSS or Babel for JavaScript offer additional features and simplify code development.

To transpile our code, we will use Babel - a JavaScript compiler, that will generate files Node.js is happy with, and Webpack - a JavaScript bundler, that will bundle our code and automate the compilation step.

Can be used with promises, Node-style callbacks, ES6 generators and async/await (using Babel).