Version Guard

Used to ensure modern CLI scripts fail silently on old node.js versions

Usage

Add a top-level file to your project, eg. cli.js, containing something like:

require('version-guard')('./path/to/file/to/run', 14, 18);

Syntax

versionGuard(filePath, minMajor, [minMinor])

• filePath - a path to the modern file that should be run
• minMajor - the lowest major Node.js version that should be allowed to run the file
• [minMinor] - the lowest minor version of minMajor that should be allowed to run the file

On supported versions imports and runs filePath using the dynamic import() (supporting both ESM and CJS modules).

On non-supported versions, fails silently with an error message.

Apart from checking current node version this command also looks up the main project's package.json and checks that the engines.node in it mentions the same version number as is sent to this command. To ensure that maintainers doesn't forget to update one of the two and thus the two diverging.

Notes

This project itself is a CJS project as the entire point is to work on incredibly old node.js versions.

Used by

• dependency-check - in progress
• installed-check - in progress

Current Tags

• 1.1.1                                ...           latest (a year ago)

5 Versions

• 1.1.1                                ...           a year ago
• 1.1.0                                ...           2 years ago
• 1.0.2                                ...           2 years ago
• 1.0.1                                ...           2 years ago
• 1.0.0                                ...           2 years ago