Configuring NPM

JavaScript & Node Package Manager (NPM)

Recommended: Node 18+ & NPM 10.2.4+
Minimum Required: Node 10+ & NPM 7.11+

All NES Products are designed and delivered to work with NPM, the default package manager for JavaScript and TypeScript. Our products are delivered via a scoped private registry, and make use of protocol aliases* and overrides to ensure your project AND all transitive dependencies do not include the unsupported Open Source distributions.

Notes

We do not support other installation methods such as: Nuget, PIP, Gems, and others.
- While we do not officially support these methods, these can potentially be configured to download directly or via an npm-powered build step.
While the minimum requirements list Node 10 and above, versions prior to Node 18 are both End Of Life and likely require additional configurations (such as forced installations, which disables important security features).
For those running Node < 10 that view upgrading as a non-starter: while we strongly recommend upgrading to at least a supported Node runtime (Node 18 is the oldest LTS, at the time of this writing), we have had reports of customers successfully migrating to Node 14 with minimal efforts from versions as old as Node 4 (circa 2005).
NPM's protocol aliases documentation does not explicitly reference the npm:<package> resolution process, but it is a well-known feature that has been confirmed by NPM to be supported for years to come.

Alternative Methods

Not using NPM? No problem! We support multiple download methods for obtaining our packages.

While we have many customers who have reported success with nearly every known package manager, we explicitly do NOT provide support for Yarn (neither v1 / v2) and Bower. Both have known issues supporting scoped registries, and migration to NPM for package management is trivial for most affected projects.