Downloads:

2,973,992

Downloads of v 0.10.8:

659

Last Update:

25 May 2013

Package Maintainer(s):

Software Author(s):

  • Joyent

Tags:

nodejs node javascript

Node JS

This is not the latest version of Node JS available.

  • 1
  • 2
  • 3

0.10.8 | Updated: 25 May 2013

Downloads:

2,973,992

Downloads of v 0.10.8:

659

Maintainer(s):

Software Author(s):

  • Joyent

  • 1
  • 2
  • 3
Node JS 0.10.8

This is not the latest version of Node JS available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Unknown


Verification Testing Unknown


Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Node JS, run the following command from the command line or from PowerShell:

>

To upgrade Node JS, run the following command from the command line or from PowerShell:

>

To uninstall Node JS, run the following command from the command line or from PowerShell:

>

Deployment Method:

📝 NOTE: 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

  • 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

3. Copy Your Script

choco upgrade nodejs -y --source="'INTERNAL REPO URL'" --version="'0.10.8'" [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 -y --source="'INTERNAL REPO URL'" --version="'0.10.8'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install nodejs
  win_chocolatey:
    name: nodejs
    version: '0.10.8'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'nodejs' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.10.8'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller nodejs
{
    Name     = "nodejs"
    Version  = "0.10.8"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'nodejs':
  ensure   => '0.10.8',
  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.

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 27 Jan 2015.

Description

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

This package is an alias for the nodejs.commandline package, which simply installs Node.exe to the Chocolatey folder. Does not include NPM.


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.

Add to Builder Version Downloads Last Updated Status
Node JS 18.9.0 18160 Thursday, September 8, 2022 Approved
Node JS 18.8.0 16679 Wednesday, August 24, 2022 Approved
Node JS 18.7.0 30458 Wednesday, July 27, 2022 Approved
Node JS 18.6.0 16815 Thursday, July 14, 2022 Approved
Node JS 18.5.0 9665 Thursday, July 7, 2022 Approved
Node JS 18.4.0 22742 Thursday, June 16, 2022 Approved
Node JS 18.3.0 17356 Thursday, June 2, 2022 Approved
Node JS 17.9.1 218 Thursday, June 2, 2022 Approved
Node JS 17.9.0 50789 Friday, April 8, 2022 Approved
Discussion for the Node JS Package

Ground Rules:

  • This discussion is only about Node JS and the Node JS 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 Node JS, 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