@brigand/assert-node-version
Advanced tools
Asserts the node version against one from the package.json or .nvmrc file
A module to assert the current node version against the one in the package.json or .nvmrc file.
// directory can be a directory which is used to lookup the node version
// `process.cwd()` is used as default directory
// The method throws an error if the version isn't satisfied
require('@brigand/assert-node-version')([directory])
When using import statements, you may prefer to import the 'auto' module which does the assertion
without requiring a function call.
import '@brigand/assert-node-version/auto';
// or
require('@brigand/assert-node-version/auto');
In version 2, if the version is only digits and periods, it will be interpreted as if it began
with a caret (i.e. semver compatible). Prefix the version with an = to get the 1.x behavior.
FAQs
Asserts the node version against one from the package.json or .nvmrc file
We found that @brigand/assert-node-version demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.
Security News
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.