Engines Packages

Install different versions of dependencies depending on which version of Node you are using

outdated versions checker for Node.js engines

Ensure that node is run as the correct version, and uses --harmony, if needed

Test User eXperience Harness

Render engine requirements in Markdown files via Markdown Magic

warns users about incompatible Node.js versions per engines in package.json

Convert a version expression to released Node.js versions (by full or partial semver, expression, or package.json engines.node)

Check engines you have defined in a file or `package.json` section that satisfies your global or locally program.

Demand a Node or npm version to run your app.

A middleware that setups view engines path

Use glob patterns to load an array of requireable files or npm modules - like plugins or middleware, optionally passing a config object to each module.

Turns dynamic pages into static pages to be indexed by search engines.

Add engines field to your package.json file in current working directory or user-defined directory

'node' and 'npm' replacement that uses versions from package.json/engines.

Checks package.json engines to match with global or local binaries.

Demand a Node or npm version to run your app.

An opinionated cli tool to migrate Ember components from app to addons within a Yarn workspace.

bem engines middleware to make bundles on render

Collection of wrapped view engines that cannot be directly used with TrashPanda

validate all engine versions from package.json