We currently support two package installation methods:
- using a compatible npm client
- downloading a tarball (
The current list of compatible and verified package managers is:
- npm v6.9.0+
- npm v7.11.0+
- npm v8
- npm v9
- npm v10
- Yarn v2
- Yarn v3
- pnpm v5
- pnpm v6
- pnpm v7
- pnpm v8
- Maven using tarball downloads
We do not currently support other installation methods such as: Nuget, PIP, Gems, and others.
While we do not officially support these methods, some of these can potentially be configured to work with our REST API, tarball download, or the npm protocol.
It is not possible for us to ever support the following package managers:
- Yarn v1
- npm versions falling between 6.0.0 and 6.8.0. These versions do not support installing packages using an alias. See the changelog note here for version 6.9.0 where support was added for using aliases when installing packages.
- npm versions falling between 7.0.0 and 7.10.0. This is due to a bug in npm related to installing packages using an alias when authentication is required.
We support the following Enterprise Package Registries:
- jFrog Artifactory
- Sonatype Nexus
Artifactory requires additional credentials and we provide a custom document for configuring it for us with the HeroDevs registry. Nexus is compatible with our standard credentials.
We are open to supporting additional Enterprise Package Registries, if you need another registry to be supported, please reach out to our support team.