Downloads:
300,774
Downloads of v 1.1.12:
107,569
Last Update:
28 Nov 2023
Package Maintainer(s):
Software Author(s):
- coreybutler
Tags:
nvm node nodejs node.js version manager windows- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
NVM
- 1
- 2
- 3
1.1.12 | Updated: 28 Nov 2023
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
300,774
Downloads of v 1.1.12:
107,569
Software Author(s):
- coreybutler
NVM 1.1.12
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by coreybutler. The inclusion of coreybutler trademark(s), if any, upon this webpage is solely to identify coreybutler goods or services and not for commercial purposes.
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
Deployment Method: Individual Install, Upgrade, & Uninstall
To install NVM, run the following command from the command line or from PowerShell:
To upgrade NVM, run the following command from the command line or from PowerShell:
To uninstall NVM, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download nvm.install --internalize --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade nvm.install -y --source="'INTERNAL REPO URL'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade nvm.install -y --source="'INTERNAL REPO URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install nvm.install
win_chocolatey:
name: nvm.install
version: '1.1.12'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'nvm.install' do
action :install
source 'INTERNAL REPO URL'
version '1.1.12'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller nvm.install
{
Name = "nvm.install"
Version = "1.1.12"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'nvm.install':
ensure => '1.1.12',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...
This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.
- Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
- Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
- Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.
Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.
This package was approved by moderator Windos on 28 Nov 2023.
NVM
Overview
Manage multiple installations of node.js on a Windows computer.
This has always been a node version manager, not an io.js manager, so there is no back-support for io.js. Node 4+ is supported. Remember when running nvm install
or nvm use
, Windows usually requires administrative rights (to create symlinks).
There are situations where the ability to switch between different versions of Node.js can be very useful. For example, if you want to test a module you're developing with the latest bleeding edge version without uninstalling the stable version of node, this utility can help.
Usage
nvm-windows runs in an admin shell. You'll need to start Powershell
or Command Prompt
as Administrator to use nvm-windows
.
NVM for Windows is a command line tool. Simply type nvm
in the console for help. The basic commands are:
nvm arch [32|64]
: Show if node is running in 32 or 64 bit mode. Specify 32 or 64 to override the default architecture.nvm current
: Display active version.nvm install ﹤version﹥ [arch]
: The version can be a specific version, "latest" for the latest current version, or "lts" for the most recent LTS version. Optionally specify whether to install the 32 or 64 bit version (defaults to system arch). Set [arch] to "all" to install 32 AND 64 bit versions. Add--insecure
to the end of this command to bypass SSL validation of the remote download server.nvm list [available]
: List the node.js installations. Typeavailable
at the end to show a list of versions available for download.nvm on
: Enable node.js version management.nvm off
: Disable node.js version management (does not uninstall anything).nvm proxy [url]
: Set a proxy to use for downloads. Leave[url]
blank to see the current proxy. Set[url]
to "none" to remove the proxy.nvm uninstall ﹤version﹥
: Uninstall a specific version.nvm use ﹤version﹥ [arch]
: Switch to use the specified version. Optionally uselatest
,lts
, ornewest
.newest
is the latest installed version. Optionally specify 32/64bit architecture.nvm use ﹤arch﹥
will continue using the selected version, but switch to 32/64 bit mode. For information about usinguse
in a specific directory (or using.nvmrc
), please refer to issue #16.nvm root ﹤path﹥
: Set the directory where nvm should store different versions of node.js. If﹤path﹥
is not set, the current root will be displayed.nvm version
: Displays the current running version of NVM for Windows.nvm node_mirror ﹤node_mirror_url﹥
: Set the node mirror.nvm npm_mirror ﹤npm_mirror_url﹥
: Set the npm mirror.
# Set error action preference to stop on errors
$ErrorActionPreference = 'Stop'
# Define package configuration
$packageName = 'nvm.install'
$packageSearch = 'NVM for Windows*'
$fileType = 'exe'
$silentArgs = '/SILENT /SUPPRESSMSGBOXES'
$validExitCodes = @(0)
# Registry paths to search for installed packages
$registryPaths = @(
'HKLM:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*',
'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*',
'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*'
)
# Search and uninstall the package
$registryPaths | ForEach-Object {
Get-ItemProperty -Path $_ -ErrorAction SilentlyContinue |
Where-Object { $_.DisplayName -like $packageSearch } |
ForEach-Object {
Uninstall-ChocolateyPackage -PackageName $packageName `
-FileType $fileType `
-SilentArgs $silentArgs `
-File ($_.UninstallString -replace '"', '') `
-ValidExitCodes $validExitCodes
}
}
Log in or click on link to see number of positives.
- nvm-setup.zip (4e076c1b80db) - ## / 66
- nvm.install.1.1.12.nupkg (7b8e471ed506) - ## / 64
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
NVM 1.1.12 | 107569 | Tuesday, November 28, 2023 | Approved | |
NVM 1.1.11 | 90251 | Friday, April 14, 2023 | Approved | |
NVM 1.1.10 | 14749 | Monday, March 13, 2023 | Approved | |
NVM 1.1.9 | 88205 | Sunday, February 13, 2022 | Approved |
Copyright (c) 2022 Ecor Ventures LLC.
This package has no dependencies.
Ground Rules:
- This discussion is only about NVM and the NVM package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or NVM, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.