Sign in

Minimum Requirements

Given the increasingly diverse technology ecosystems that NES products operate in, there are instances where certain tools & runtimes require specific environmental factors. These could be minimum versions for build toolchains, custom build and integration instructions, etc. 

This page will constantly be updated with the minimum requirements for each technology ecosystem we support, as well as any relevant details. As always, if there are any questions please feel free to reach out to sales@herodevs.com for more information. 

 

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. 

PHP & PHP Libraries

More PHP documentation coming soon! Please contact sales@herodevs.com if you have questions.

PHP Runtime

For PHP itself, we will be offering native installation packages (rpm, apt, etc.) for the various supported operating systems. Both the versions of PHP and target operating systems are under evaluation and will be driven by market demand, so please let sales@herodevs.com know which are important to your team. 

 

PHP Libraries

While our initial NES offerings are geared towards Drupal NES, we are also evaluating other tech stacks such as Laravel, Wordpress, and more. Please contact sales@herodevs.com to let us know more about which products and packages/modules are important to your team. 

 

Java & JVM Technologies

For Java & other JVM technologies, our registry provides first-class support for both Maven and Gradle as package managers.

We are currently evaluating the following versions for Java, Gradle, and Maven:

  • Java: 8, 11, 17
  • Gradle: 7.6.x+
  • Maven: 3.9+

Additional versions are under evaluation and will be driven by market demand. More details coming soon. If you have specific versions you are working with or have additional questions, contact sales@herodevs.com.

 

Python

While we're still early in our adoption of Python packages, we already can commit to supporting the Pip package manager. Conda and Poetry are also under evaluation, so please let sales@herodevs.com know if these (or other) package managers are important to your team. 

Additional details coming soon. Please contact sales@herodevs.com if you have questions.