nodenv-package-json-engine icon indicating copy to clipboard operation
nodenv-package-json-engine copied to clipboard

Activate a nodenv node version from package.json#engines.node field

Results 4 nodenv-package-json-engine issues
Sort by recently updated
recently updated
newest added
trafficstars

Significant refactor to support the traditional subcommand/bin/libexec structure of nodenv plugins. - Removes `plugin_root` from bin, so we aren't polluting user's PATH with more stuff. - adds nodenv-package-json which provides...

in progress

Hey there :wave: Would you consider an auto-installation feature in your plugin? Right now, I'm relying on multiple project/hooks/configurations on my setup to achieve that (e.g.: watch the `package.json` file,...

> Once you've installed the plugin you can verify that it's working by cding into a project that has a package.json file with engines and does not have a .node-version...

After #50, it will be nice to have parity with the `shell`, `local`, and `global` subcommands to be able to set the version spec in engines. This json parse may...