@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
The npm package @jsii/check-node receives a total of 213,841 weekly downloads. As such, @jsii/check-node popularity was classified as popular.
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.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
Research
Security News
Socket researchers uncovered a backdoored typosquat of BoltDB in the Go ecosystem, exploiting Go Module Proxy caching to persist undetected for years.
Security News
Company News
Socket is joining TC54 to help develop standards for software supply chain security, contributing to the evolution of SBOMs, CycloneDX, and Package URL specifications.