henrynguyen5 / vsc-nvm

VSCode extension based NVM helper

README

Install here

Simplify your node versioning workflow with nvm and this extension.

Features

This extension simplifies nvm workflow by:

• Automatically running nvm use on each terminal opened when an .nvmrc file exists in your workspace. Inspired by vscode-nvm
• Providing a command input hook to choose a version of node to run tasks against

Requirements

• To be able to pick different node versions, you must have nvm installed
• To have nvm use executed on terminal startup, you must have nvm installed along with a .nvmrc file in your workspace

Extension Settings

Running a task with a choosable node version

// launch.json for running version picker with defaults
{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "launch",
      "name": "Jest Current File",
      "program": "${workspaceFolder}/node_modules/.bin/jest",
      "args": ["--detectOpenHandles", "${relativeFile}"],
      "console": "integratedTerminal",
      "internalConsoleOptions": "neverOpen",
      "runtimeExecutable": "${env:HOME}/.nvm/versions/node/${input:pickVersion}/bin/node"
    }
  ],
  "inputs": [
    {
      "id": "pickVersion",
      "type": "command",
      "command": "extension.node-version"
    }
  ]
}

Running a task with a choosable node version in a custom nvm directory

// launch.json for running version picker with specified nvm dir
{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "launch",
      "name": "Jest Current File",
      "program": "${workspaceFolder}/node_modules/.bin/jest",
      "args": ["--detectOpenHandles", "${relativeFile}"],
      "console": "integratedTerminal",
      "internalConsoleOptions": "neverOpen",
      "runtimeExecutable": "${env:HOME}/.nvm/versions/node/${input:pickVersion}/bin/node"
    }
  ],
  "inputs": [
    {
      "id": "pickVersion",
      "type": "command",
      "command": "extension.node-version",
      "args": {
        "nvmDir": "/my/home/.nvm"
      }
    }
  ]
}

vsc-nvm's Issues

Convert to toolkit

Include things like pasting in json data to create typescript typings

It doesn't work on win10

A version argument is required but missing.

nvm use
A version argument is required but missing.
more .\.nvmrc
v19.1.0

looking into package.json "engines.node"

In order to save us from adding one more configuration file to a project and for some projects we can't even do that, is it possible to actually look into the engines.node if there's no .nvmrc file?

in the packages.json you often find this information already as

  "engines": {
    "node": "14.16.1",
    "npm": "6.14.12"
  },

[Feature request] Run `nvm use` when opening a terminal in a folder with .nvmrc

Some projects only have an .nvmrc file in a subdirectory (or different ones in different subdirectories).

It would be cool if instead of only activating when .nvmrc is in the root, on a terminal opening we check if the directory or any parent directories have an .nvmrc file and then run the nvm use command.

I think nvm use automatically checks parent directories, so might be able to get this behavior by just changing workspaceContains:.nvmrc to workspaceContains:**/.nvmrc.