It is pretty standard for those in the JavaScript world that dynamic and revolutionary changes in this area are regular. Changes are often, but the su

Building NPM package in 2021

submited by
Style Pass
2021-06-27 20:30:01

It is pretty standard for those in the JavaScript world that dynamic and revolutionary changes in this area are regular. Changes are often, but the support of the major browsers and Node engine was not so active till now.

We can agree that this is quite normal because the work on all the engines in a very dynamic environment requires time and many iterations. And all that backward compatibility is a sort of pain. Still, I guess it's ok, and it is good in the process.

In the JS world, we had at least two significant milestones. The first one was EcmaScript5, and the next was EcmaScript6, also known as ES2015, which is IMO a better naming convention, especially since we have pretty regular updates from this version. So I will use that naming convention. It is much more descriptive and will help when describing how important was ES2015 and how much time had to pass to support built-in modules and all other cool features fully.

At the time of writing this, it is 2021. Not so long ago, the Ecma General Assembly accepted the new ES2021 standard and features, but let's focus on ES2020 in general and the preparation process of the NPM packages for modern browsers and Node.

Leave a Comment