Downloads of v 6.11.0:


Last Update:

21 Jun 2017

Package Maintainer(s):

Software Author(s):

  • Joyent


nodejs node javascript

[DEPRECATED] Node JS (Portable, CommandLine)

  • 1
  • 2
  • 3

6.11.0 | Updated: 21 Jun 2017



Downloads of v 6.11.0:


Software Author(s):

  • Joyent

  • 1
  • 2
  • 3
[DEPRECATED] Node JS (Portable, CommandLine) 6.11.0

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.


To install [DEPRECATED] Node JS (Portable, CommandLine), run the following command from the command line or from PowerShell:


To upgrade [DEPRECATED] Node JS (Portable, CommandLine), run the following command from the command line or from PowerShell:


To uninstall [DEPRECATED] Node JS (Portable, CommandLine), run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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 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

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade nodejs.commandline -y --source="'STEP 3 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 nodejs.commandline -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure nodejs.commandline installed
    name: nodejs.commandline
    state: present
    version: 6.11.0
    source: STEP 3 URL

See docs at

chocolatey_package 'nodejs.commandline' do
  action    :install
  version  '6.11.0'
  source   'STEP 3 URL'

See docs at

    Name: nodejs.commandline,
    Version: 6.11.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller nodejs.commandline
   Name     = 'nodejs.commandline'
   Ensure   = 'Present'
   Version  = '6.11.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'nodejs.commandline':
  provider => 'chocolatey',
  ensure   => '6.11.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install nodejs.commandline version="6.11.0" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

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 as a trusted package on 09 Jul 2020.



This package uses an older NPM which is no longer offered as a standalone package separately from NodeJS. It is recommended that you uninstall this package and the package nodejs.commandline in favor of nodejs.install (which nodejs package now points to).

Use nodejs.install instead (Node JS package (nodejs) now points to nodejs.install).


Node JS - Evented I/O for v8 JavaScript. Node's goal is to provide an easy way to build scalable network programs.

This package simply copies Node.exe to a subfolder within the Chocolatey folder. This now takes a dependency on the npm package, so NPM will be installed as well.

$packageName = 'nodejs'
$url = ''
$url64 = ''

try {
  $installDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

  $nodePath = Join-Path $installDir 'node.exe'
  Get-ChocolateyWebFile "$packageName" "$nodePath" "$url" "$url64"

  Write-ChocolateySuccess "$packageName"
} catch {
  Write-ChocolateyFailure "$packageName" "$($_.Exception.Message)"

Log in or click on link to see number of positives.

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.

Version Downloads Last Updated Status
[DEPRECATED] Node JS (Portable, CommandLine) 6.9.5 935 Friday, February 3, 2017 Approved
[DEPRECATED] Node JS (Portable, CommandLine) 6.9.4 377 Friday, February 3, 2017 Approved
[DEPRECATED] Node JS (Portable, CommandLine) 6.9.3 344 Friday, February 3, 2017 Approved
[DEPRECATED] Node JS (Portable, CommandLine) 5.10.1 914 Wednesday, April 6, 2016 Approved
[DEPRECATED] Node JS (Portable, CommandLine) 5.10.0 417 Friday, April 1, 2016 Approved
[DEPRECATED] Node JS (Portable, CommandLine) 5.9.1 435 Wednesday, March 23, 2016 Approved
[DEPRECATED] Node JS (Portable, CommandLine) 5.9.0 430 Wednesday, March 16, 2016 Approved
[DEPRECATED] Node JS (Portable, CommandLine) 5.8.0 446 Thursday, March 10, 2016 Approved
[DEPRECATED] Node JS (Portable, CommandLine) 5.7.1 385 Thursday, March 3, 2016 Approved
Discussion for the [DEPRECATED] Node JS (Portable, CommandLine) Package

Ground Rules:

  • This discussion is only about [DEPRECATED] Node JS (Portable, CommandLine) and the [DEPRECATED] Node JS (Portable, CommandLine) 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 [DEPRECATED] Node JS (Portable, CommandLine), 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.
comments powered by Disqus