![]() I show you all these now to give you an idea how many new features have released since es8/2017. As vendors improve support for that new version, they are exposed to developers in their products (like browsers and NodeJS). Hopefully you have some idea of the versions and timelines now, but why does it matter? Because each new ecmaScript version defines new features. When we make the move to Node 18.x, then we will have support for es version 13 aka es2022. Since we are still on NodeJS 14, ecmaScript support is limited currently to es11 or es2020. ![]() Right now es version 13 also known as es2022 is stable, BUT support for it in Node isn't stable until version 17.9.1 (97% coverage). Support for a given version is entirely dependent on the environment such as node vs browser, which browser, which version of that browser and such. What we know today as Javascript, is really vendor-specific implementations of ecmascript.Įcmascript didn't really gain traction until version 6 and it has continued to evolve since. Javascript was originally created for Netscape and before it went down, a project was started to formalize the language and that became ecmascript. The creator Brendan Eich set out to create a language like, but simpler than Java.
0 Comments
Leave a Reply. |