@jsii/check-node
Advanced tools
@jsii/check-nodeThis package can be used to check whether the node runtime used to run an
application is known to be compatible with the jsii constellation of packages,
and emits a warning to STDERR in case this is not the case.
Either import the checkNode function from the root of the package, and run it
wherever it makes sense (often at the entry point of command line tools):
import { checkNode } from '@jsii/check-node';
// ...
checkNode();
// ...
Alternatively, import @jsii/check-node/run in the location where the check
should be performed. This is particularly useful when some of the modules
imported by a command line tool may fail loading in unsupported runtimes, and
hence the check must run before these are imported.
import '@jsii/check-node/run';
FAQs
Checks for supported node versions
We found that @jsii/check-node demonstrated a healthy version release cadence and project activity because the last version was released less than 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.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.