Feature request: Testing for NPM package publishing

[fordN]

In order to ensure NPM packages build successfully for our users in different environments let's get in the habit of testing package publishing with each PR merge.

A few options:

• Use a local, private registry built with Verdaccio (or similar) to test package publishing locally.
• Setup a hosted registry using Verdaccio (or similar) which is automatically published to with every PR merge. This approach would provide a publicly accessible registry with all canary builds that indexers can test.
• Use a similar approach to previous but deploy to the official NPM registry using alpha or canary tags.

[fordN]

I'm leaning towards the third option for its implementation simplicity and natural transparency. As long as we use a clear tag such as canary or alpha to separate it from latest users aren't likely to accidentally install on production machines and this will be a good step towards a more automated/regular release pattern.

[saihaj]

not following why we need to test publishing of packages? We already have CI jobs where we are building across multiple Node JS versions and running tests on.