Step 1: Review Your Packages

Step 2: Choose Your Integration Method

Step 3: Copy Your Script or Download Config

Option 1: Copy Script

Option 2: Download Config

Step 4: 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 packages and push them to a repository
  Download Packages

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the packages:
  Download Packages
- Follow manual internalization instructions
Package Internalizer (C4B)
- Run: (additional options)
- For package and dependencies run:
- Automate package internalization

Step 5: Copy Your Script

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:

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###

#### We initialize a few things that are needed by this script - there are no other requirements.
$ErrorActionPreference = "Stop"

#### Set TLS 1.2 (3072) as that is the minimum required by various up-to-date repositories.
#### Use integers because the enumeration value for TLS 1.2 won't exist
#### in .NET 4.0, even though they are addressable if .NET 4.5+ is
#### installed (.NET 4.5 is an in-place upgrade).
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072

#### We use this variable for future REST calls.
$RequestArguments = @{
    UseBasicParsing = $true
}

## 2. TOP LEVEL VARIABLES ##

### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$NugetRepositoryUrl = "INTERNAL REPO URL"

### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# $NugetRepositoryCredential = [PSCredential]::new(
#     "username",
#     ("password" | ConvertTo-SecureString -AsPlainText -Force)
# )
# $RequestArguments.Credential = $NugetRepositoryCredential

### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it
$ChocolateyDownloadUrl = "$($NugetRepositoryUrl.TrimEnd('/'))/package/chocolatey.2.2.2.nupkg"

### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"

#### ii. If using a Client Salt, add it here
# $ChocolateyCentralManagementClientSalt = "clientsalt"

#### iii. If using a Service Salt, add it here
# $ChocolateyCentralManagementServiceSalt = "servicesalt"

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository

#### Download the Nupkg, appending .zip to the filename to handle archive cmdlet limitations
if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
    $TempDirectory = Join-Path $env:Temp "chocolateyInstall"
    if (-not (Test-Path $TempDirectory -PathType Container)) {
        $null = New-Item -Path $TempDirectory -ItemType Directory
    }
    $DownloadedNupkg = Join-Path $TempDirectory "$(Split-Path $ChocolateyDownloadUrl -Leaf).zip"
    Invoke-WebRequest -Uri $ChocolateyDownloadUrl -OutFile $DownloadedNupkg @RequestArguments

    #### Extract the Nupkg, and run the chocolateyInstall script
    if (Get-Command Microsoft.PowerShell.Archive\Expand-Archive -ErrorAction SilentlyContinue) {
        Microsoft.PowerShell.Archive\Expand-Archive -Path $DownloadedNupkg -DestinationPath $TempDirectory -Force
    } else {
        # PowerShell versions <4.0 do not have this function available
        try {
            $shellApplication = New-Object -ComObject Shell.Application
            $zipPackage = $shellApplication.NameSpace($DownloadedNupkg)
            $destinationFolder = $shellApplication.NameSpace($TempDirectory)
            $destinationFolder.CopyHere($zipPackage.Items(), 0x10)
        } catch {
            Write-Warning "Unable to unzip package using built-in compression."
            throw $_
        }
    }

    & $(Join-Path $TempDirectory "tools\chocolateyInstall.ps1")
}

if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
    refreshenv
}

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# choco feature enable -n useFipsCompliantChecksums

### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
choco config set --name cacheLocation --value C:\ProgramData\chocolatey\cache

#### Increase timeout to at least 4 hours
choco config set --name commandExecutionTimeoutSeconds --value 14400

#### Turn off download progress when running choco through integrations
choco feature disable --name showDownloadProgress

### c. Sources ###
#### Remove the default community package repository source
choco source list --limitoutput | ConvertFrom-Csv -Header 'Name', 'Location' -Delimiter '|' | ForEach-Object {
    if ($_.Location -eq 'https://community.chocolatey.org/api/v2/') {
        choco source remove -n $_.Name
    }
}

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE may require changes
if ($NugetRepositoryCredential) {
    choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --user $NugetRepositoryCredential.UserName --password $NugetRepositoryCredential.GetNetworkCredential().Password --priority 1
} else {
    choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --priority 1
}

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
choco upgrade chocolatey --confirm

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
choco install chocolatey-license --source $NugetRepositoryUrl --confirm

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
    choco source disable --name chocolatey.licensed
} else {
    Write-Warning "Not disabling 'chocolatey.licensed' feed, as Chocolatey-License has not been installed."
}

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
    choco install chocolatey.extension --source $NugetRepositoryUrl --confirm
} else {
    Write-Warning "Not installing 'chocolatey.extension', as Chocolatey-License has not been installed."
}

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
choco feature disable --name showNonElevatedWarnings
choco feature enable --name useBackgroundService
choco feature enable --name useBackgroundServiceWithNonAdministratorsOnly
choco feature enable --name allowBackgroundServiceUninstallsFromUserInstallsOnly
choco config set --name allowedBackgroundServiceCommands --value "install,upgrade,uninstall"

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if ($ChocolateyCentralManagementUrl) {
    choco install chocolatey-agent --source $NugetRepositoryUrl --confirm
    choco config set --name CentralManagementServiceUrl --value $ChocolateyCentralManagementUrl
    if ($ChocolateyCentralManagementClientSalt) {
        choco config set --name centralManagementClientCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementClientSalt
    }
    if ($ChocolateyCentralManagementServiceSalt) {
        choco config set --name centralManagementServiceCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementServiceSalt
    }
    choco feature enable --name useChocolateyCentralManagement
    choco feature enable --name useChocolateyCentralManagementDeployments
}

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

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. chocolatey.chocolatey
##### You will require the chocolatey.chocolatey collection to be installed
##### on all machines using this playbook.
##### Please see https://github.com/chocolatey/chocolatey-ansible/#installing-the-collection-from-ansible-galaxy

- name: Install and Configure Chocolatey
  hosts: all

## 2. TOP LEVEL VARIABLES ##
  vars:

### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
    nuget_repository_url: INTERNAL REPO URL

### b. Internal Repository Credential ###
#### If required, add the repository access credential here and
#### uncomment lines with source_username and source_password below
#    nuget_repository_username: username
#    nuget_repository_password: password

### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
#    chocolatey_central_management_url: https://chocolatey-central-management:24020/ChocolateyManagementService

#### ii. If using a Client Salt, add it here
#    chocolatey_central_management_client_salt: clientsalt

#### iii. If using a Service Salt, add it here
#    chocolatey_central_management_service_salt: servicesalt

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository

  tasks:
  - name: Install chocolatey
    win_chocolatey:
      name: chocolatey
      source: ""{{ nuget_repository_url }}""
      # source_username: ""{{ nuget_repository_username }}""
      # source_password: ""{{ nuget_repository_password }}""

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#   - name: Enable FIPS compliance
#     win_chocolatey_feature:
#       name: useFipsCompliantChecksums
#       state: enabled

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
  - name: Set the cache location
    win_chocolatey_config:
      name: cacheLocation
      state: present
      value: C:\ProgramData\chocolatey\cache

#### Increase timeout to at least 4 hours
  - name: Set the command execution timeout
    win_chocolatey_config:
      name: commandExecutionTimeoutSeconds
      state: present
      value: 14400

#### Turn off download progress when running choco through integrations
  - name: Disable showing download progress
    win_chocolatey_feature:
      name: showDownloadProgress
      state: disabled

### c. Sources ###
#### Remove the default community package repository source
  - name: Remove Chocolatey Community Repository
    win_chocolatey_source:
      name: chocolatey
      state: absent

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
  - name: Add Internal Repository
    win_chocolatey_source:
      name: ChocolateyInternal
      state: present
      source: {{ nuget_repository_url }}
      # source_username: {{ nuget_repository_username }}
      # source_password: {{ nuget_repository_password }}
      priority: 1

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
  - name: Upgrade Chocolatey
    win_chocolatey:
      name: chocolatey
      state: latest

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
  - name: Install Chocolatey License
    win_chocolatey:
      name: chocolatey-license
      source: ChocolateyInternal
      state: latest

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
  - name: Disable Chocolatey Community Repository
    win_chocolatey_source:
      name: chocolatey.licensed
      state: disabled

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
  - name: Install Chocolatey Extension
    win_chocolatey:
      name: chocolatey.extension
      source: ChocolateyInternal
      state: latest

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
  - name: Hide not-elevated warnings
    win_chocolatey_feature:
      name: showNonElevatedWarnings
      state: disabled

  - name: Use background mode for self-service
    win_chocolatey_feature:
      name: useBackgroundService
      state: enabled

  - name: Use background service for non-admins
    win_chocolatey_feature:
      name: useBackgroundServiceWithNonAdministratorsOnly
      state: enabled

  - name: Allow background uninstallation for user installs
    win_chocolatey_feature:
      name: allowBackgroundServiceUninstallsFromUserInstallsOnly
      state: enabled

  - name: Set allowed background service commands
    win_chocolatey_config:
      name: backgroundServiceAllowedCommands
      state: present
      value: install,upgrade,uninstall

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
  - name: Install Chocolatey Agent
    when: chocolatey_central_management_url is defined
    win_chocolatey:
      name: chocolatey-agent
      source: ChocolateyInternal
      state: latest

  - name: Set the Central Management Service URL
    when: chocolatey_central_management_url is defined
    win_chocolatey_config:
      name: CentralManagementServiceUrl
      state: present
      value: {{ chocolatey_central_management_url }}

  - name: Set the Central Management Client Salt
    when: chocolatey_central_management_client_salt is defined
    win_chocolatey_config:
      name: centralManagementClientCommunicationSaltAdditivePassword
      state: present
      value: {{ chocolatey_central_management_client_salt }}

  - name: Set the Central Management Service Salt
    when: chocolatey_central_management_service_salt is defined
    win_chocolatey_config:
      name: centralManagementServiceCommunicationSaltAdditivePassword
      state: present
      value: {{ chocolatey_central_management_service_salt }}

  - name: Use Central Management
    when: chocolatey_central_management_url is defined
    win_chocolatey_feature:
      name: useChocolateyCentralManagement
      state: enabled

  - name: Use Central Management Deployments
    when: chocolatey_central_management_url is defined
    win_chocolatey_feature:
      name: useChocolateyCentralManagementDeployments
      state: enabled

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

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### The Chocolatey resources are available with any recent version of Chef.
#### We utilise the Chocolatey recipe to install the Chocolatey binaries.
include_recipe "chocolatey"

## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
NugetRepositoryUrl = "INTERNAL REPO URL"

### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# NugetRepositoryUsername = "username"
# NugetRepositoryPassword = "password"

### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
ChocolateyNupkgUrl = "INTERNAL REPO URL/package/chocolatey.2.2.2.nupkg",

### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"

#### ii. If using a Client Salt, add it here
# ChocolateyCentralManagementClientSalt = "clientsalt"

#### iii. If using a Service Salt, add it here
# ChocolateyCentralManagementServiceSalt = "servicesalt"

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
node['chocolatey']['install vars'] = {
  'chocolateyDownloadUrl' => "#{ChocolateyNupkgUrl}",
}

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# chocolatey_feature 'useFipsCompliantChecksums' do
#   action :enable
# end

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolatey_config 'cacheLocation' do
  value 'C:\ProgramData\chocolatey\cache'
end

#### Increase timeout to at least 4 hours
chocolatey_config 'commandExecutionTimeoutSeconds' do
  value '14400'
end

#### Turn off download progress when running choco through integrations
chocolatey_feature 'showDownloadProgress' do
  action :disable
end

### c. Sources ###
#### Remove the default community package repository source
chocolatey_source 'chocolatey' do
  action :remove
end

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE may require changes
chocolatey_source 'ChocolateyInternal' do
  source "#{NugetRepositoryUrl}"
  priority 1
  action   :add
end

execute 'ChocolateyInternal' do
  command "choco source add --name ChocolateyInternal -s #{NugetRepositoryUrl} -u=#{NugetRepositoryUsername} -p=#{NugetRepositoryPassword} --priority=1"
  only_if { NugetRepositoryUsername != nil || NugetRepositoryPassword != nil }
end

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
chocolatey_package 'chocolatey' do
  action :upgrade
  source "#{NugetRepositoryUrl}"
end

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
chocolatey_package 'chocolatey-license' do
  action :install
  source "#{NugetRepositoryUrl}"
end

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
chocolatey_source 'chocolatey.licensed' do
  action            :disable
end

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
chocolatey_package 'chocolatey.extention' do
  action     install
  source     "#{NugetRepositoryUrl}"
end

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolatey_feature 'showNonElevatedWarnings' do
  action :disable
end

chocolatey_feature 'useBackgroundService' do
  action :enable
end

chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
  action :enable
end

chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
  action :enable
end

chocolatey_config 'backgroundServiceAllowedCommands' do
  value 'install,upgrade,uninstall'
end

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
chocolatey_package 'chocolatey-agent' do
  action     install
  source     "#{NugetRepositoryUrl}"
  # user       "#{NugetRepositoryUsername}"
  # password   "#{NugetRepositoryPassword}"
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_config 'CentralManagementServiceUrl' do
  value  "#{ChocolateyCentralManagementUrl}"
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_config 'centralManagementClientCommunicationSaltAdditivePassword' do
  value   "#{ChocolateyCentralManagementClientSalt}"
  only_if { ChocolateyCentralManagementClientSalt != nil }
end

chocolatey_config 'centralManagementServiceCommunicationSaltAdditivePassword' do
  value   "#{ChocolateyCentralManagementServiceSalt}"
  only_if { ChocolateyCentralManagementServiceSalt != nil }
end

chocolatey_feature 'useChocolateyCentralManagement' do
  action :enable
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_feature 'useChocolateyCentralManagementDeployments' do
  action :enable
  only_if { ChocolateyCentralManagementUrl != nil }
end

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

If Applicable - Chocolatey Configuration/Installation


#requires -Modules cChoco
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. Requires chocolatey\cChoco DSC module to be installed on the machine compiling the DSC manifest
#### NOTE: This will need to be installed before running the DSC portion of this script
if (-not (Get-Module cChoco -ListAvailable)) {
    $null = Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
    if (($PSGallery = Get-PSRepository -Name PSGallery).InstallationPolicy -ne "Trusted") {
        Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
    }
    Install-Module -Name cChoco
    if ($PSGallery.InstallationPolicy -ne "Trusted") {
        Set-PSRepository -Name PSGallery -InstallationPolicy $PSGallery.InstallationPolicy
    }
}

#### ii. Requires a hosted copy of the install.ps1 script
##### This should be available to download without authentication.
##### The original script can be found here: https://community.chocolatey.org/install.ps1

Configuration ChocolateyConfig {
## 2. TOP LEVEL VARIABLES ##
    param(
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
        $NugetRepositoryUrl      = "INTERNAL REPO URL",

### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
        $ChocolateyNupkgUrl      = "INTERNAL REPO URL/package/chocolatey.2.2.2.nupkg",

### c. Internal Repository Credential ###
#### If required, add the repository access credential here
#        $NugetRepositoryCredential = [PSCredential]::new(
#            "username",
#            ("password" | ConvertTo-SecureString -AsPlainText -Force)
#        ),

### d. Install.ps1 URL
#### The path to the hosted install script:
        $ChocolateyInstallPs1Url = "https://community.chocolatey.org/install.ps1"

### e. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
#        $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService",

#### ii. If using a Client Salt, add it here
#        $ChocolateyCentralManagementClientSalt = "clientsalt",

#### iii. If using a Service Salt, add it here
#        $ChocolateyCentralManagementServiceSalt = "servicesalt"
    )
    Import-DscResource -ModuleName PSDesiredStateConfiguration
    Import-DscResource -ModuleName cChoco

    Node 'localhost' {
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
        Environment chocoDownloadUrl {
            Name  = "chocolateyDownloadUrl"
            Value = $ChocolateyNupkgUrl
        }

        cChocoInstaller installChocolatey {
            DependsOn = "[Environment]chocoDownloadUrl"
            InstallDir = Join-Path $env:ProgramData "chocolatey"
            ChocoInstallScriptUrl = $ChocolateyInstallPs1Url
        }

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#        cChocoFeature featureFipsCompliance {
#            FeatureName = "useFipsCompliantChecksums"
#        }

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
        cChocoConfig cacheLocation {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            ConfigName = "cacheLocation"
            Value      = "C:\ProgramData\chocolatey\cache"
        }

#### Increase timeout to at least 4 hours
        cChocoConfig commandExecutionTimeoutSeconds {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            ConfigName = "commandExecutionTimeoutSeconds"
            Value      = 14400
        }

#### Turn off download progress when running choco through integrations
        cChocoFeature showDownloadProgress {
            DependsOn   = "[cChocoInstaller]installChocolatey"
            FeatureName = "showDownloadProgress"
            Ensure      = "Absent"
        }

### c. Sources ###
#### Remove the default community package repository source
        cChocoSource removeCommunityRepository {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            Name       = "chocolatey"
            Ensure     = "Absent"
        }

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here.
#### NOTE: This EXAMPLE may require changes
        cChocoSource addInternalSource {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            Name        = "ChocolateyInternal"
            Source      = $NugetRepositoryUrl
            Credentials = $NugetRepositoryCredential
            Priority    = 1
        }

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
        cChocoPackageInstaller updateChocolatey {
            DependsOn   = "[cChocoSource]addInternalSource", "[cChocoSource]removeCommunityRepository"
            Name        = "chocolatey"
            AutoUpgrade = $true
        }

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
        cChocoPackageInstaller chocolateyLicense {
            DependsOn = "[cChocoPackageInstaller]updateChocolatey"
            Name      = "chocolatey-license"
        }

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
        Script disableLicensedSource {
            DependsOn  = "[cChocoPackageInstaller]chocolateyLicense"
            GetScript  = {
                $Source = choco source list --limitoutput | `
                    ConvertFrom-Csv -Delimiter '|' -Header Name, Source, Disabled | `
                    Where-Object Name -eq "chocolatey.licensed"

                return @{
                    Result = if ($Source) {
                        [bool]::Parse($Source.Disabled)
                    } else {
                        Write-Warning "Source 'chocolatey.licensed' was not present."
                        $true  # Source does not need disabling
                    }
                }
            }
            SetScript  = {
                $null = choco source disable --name "chocolatey.licensed"
            }
            TestScript = {
                $State = [ScriptBlock]::Create($GetScript).Invoke()
                return $State.Result
            }
        }

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
        cChocoPackageInstaller chocolateyLicensedExtension {
            DependsOn = "[Script]disableLicensedSource"
            Name      = "chocolatey.extension"
        }

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
        cChocoFeature hideElevatedWarnings {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "showNonElevatedWarnings"
            Ensure      = "Absent"
        }

        cChocoFeature useBackgroundService {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "useBackgroundService"
            Ensure      = "Present"
        }

        cChocoFeature useBackgroundServiceWithNonAdmins {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "useBackgroundServiceWithNonAdministratorsOnly"
            Ensure      = "Present"
        }

        cChocoFeature useBackgroundServiceUninstallsForUserInstalls {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "allowBackgroundServiceUninstallsFromUserInstallsOnly"
            Ensure      = "Present"
        }

        cChocoConfig allowedBackgroundServiceCommands {
            DependsOn   = "[cChocoFeature]useBackgroundService"
            ConfigName = "backgroundServiceAllowedCommands"
            Value       = "install,upgrade,uninstall"
        }

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
        if ($ChocolateyCentralManagementUrl) {
            cChocoPackageInstaller chocolateyAgent {
                DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
                Name      = "chocolatey-agent"
            }

            cChocoConfig centralManagementServiceUrl {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                ConfigName = "CentralManagementServiceUrl"
                Value       = $ChocolateyCentralManagementUrl
            }

            if ($ChocolateyCentralManagementClientSalt) {
                cChocoConfig centralManagementClientSalt {
                    DependsOn  = "[cChocoPackageInstaller]chocolateyAgent"
                    ConfigName = "centralManagementClientCommunicationSaltAdditivePassword"
                    Value      = $ChocolateyCentralManagementClientSalt
                }
            }

            if ($ChocolateyCentralManagementServiceSalt) {
                cChocoConfig centralManagementServiceSalt {
                    DependsOn  = "[cChocoPackageInstaller]chocolateyAgent"
                    ConfigName = "centralManagementServiceCommunicationSaltAdditivePassword"
                    Value      = $ChocolateyCentralManagementServiceSalt
                }
            }

            cChocoFeature useCentralManagement {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                FeatureName = "useChocolateyCentralManagement"
                Ensure      = "Present"
            }

            cChocoFeature useCentralManagementDeployments {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                FeatureName = "useChocolateyCentralManagementDeployments"
                Ensure      = "Present"
            }
        }
    }
}

# If working this into an existing configuration with a good method for
$ConfigData = @{
    AllNodes = @(
        @{
            NodeName                    = "localhost"
            PSDscAllowPlainTextPassword = $true
        }
    )
}

try {
    Push-Location $env:Temp
    $Config = ChocolateyConfig -ConfigurationData $ConfigData
    Start-DscConfiguration -Path $Config.PSParentPath -Wait -Verbose -Force
} finally {
    Pop-Location
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. Requires puppetlabs/chocolatey module
####  See https://forge.puppet.com/puppetlabs/chocolatey


## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$_repository_url = 'INTERNAL REPO URL'

### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$_choco_download_url = 'INTERNAL REPO URL/package/chocolatey.2.2.2.nupkg'

### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $_chocolatey_central_management_url = 'https://chocolatey-central-management:24020/ChocolateyManagementService'

#### ii. If using a Client Salt, add it here
# $_chocolatey_central_management_client_salt = "clientsalt"

#### iii. If using a Service Salt, add it here
# $_chocolatey_central_management_service_salt = 'servicesalt'


## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
### Note: `chocolatey_download_url is completely different than normal
###  source locations. This is directly to the bare download url for the
###  chocolatey.nupkg, similar to what you see when you browse to
###  https://community.chocolatey.org/api/v2/package/chocolatey
class {'chocolatey':
  chocolatey_download_url => $_choco_download_url,
  use_7zip                => false,
}


## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations

#chocolateyfeature {'useFipsCompliantChecksums':
#  ensure => enabled,
#}

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolateyconfig {'cacheLocation':
  value => 'C:\ProgramData\chocolatey\cache',
}

#### Increase timeout to at least 4 hours
chocolateyconfig {'commandExecutionTimeoutSeconds':
  value => '14400',
}

#### Turn off download progress when running choco through integrations
chocolateyfeature {'showDownloadProgress':
  ensure => disabled,
}

### c. Sources ###
#### Remove the default community package repository source
chocolateysource {'chocolatey':
  ensure   => absent,
  location => 'https://community.chocolatey.org/api/v2/',
}

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE requires changes
chocolateysource {'internal_chocolatey':
  ensure             => present,
  location           => $_repository_url,
  priority           => 1,
  username           => 'optional',
  password           => 'optional,not ensured',
  bypass_proxy       => true,
  admin_only         => false,
  allow_self_service => false,
}

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/

package {'chocolatey':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
}


## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/guides/organizations/organizational-deployment-guide#exercise-4-create-a-package-for-the-license

# TODO: Add resource for installing/ensuring the chocolatey-license package
package {'chocolatey-license':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
}

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
## Disabled sources still need all other attributes until
## https://tickets.puppetlabs.com/browse/MODULES-4449 is resolved.
## Password is necessary with user, but not ensurable, so it should not
## matter what it is set to here. If you ever do get into trouble here,
## the password is your license GUID.
chocolateysource {'chocolatey.licensed':
  ensure   => disabled,
  priority => '10',
  user     => 'customer',
  password => '1234',
  require  => Package['chocolatey-license'],
}

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
package {'chocolatey.extension':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
  require  => Package['chocolatey-license'],
}

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolateyfeature {'showNonElevatedWarnings':
  ensure => disabled,
}

chocolateyfeature {'useBackgroundService':
  ensure => enabled,
}

chocolateyfeature {'useBackgroundServiceWithNonAdministratorsOnly':
  ensure => enabled,
}

chocolateyfeature {'allowBackgroundServiceUninstallsFromUserInstallsOnly':
  ensure => enabled,
}

chocolateyconfig {'backgroundServiceAllowedCommands':
  value => 'install,upgrade,uninstall',
}

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if $_chocolatey_central_management_url {
  package {'chocolatey-agent':
    ensure   => latest,
    provider => chocolatey,
    source   => $_repository_url,
    require  => Package['chocolatey-license'],
  }

  chocolateyconfig {'CentralManagementServiceUrl':
    value   => $_chocolatey_central_management_url,
  }

  if $_chocolatey_central_management_client_salt {
    chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
      value => $_chocolatey_central_management_client_salt,
    }
  }

  if $_chocolatey_central_management_service_salt {
    chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
      value => $_chocolatey_central_management_client_salt,
    }
  }

  chocolateyfeature {'useChocolateyCentralManagement':
    ensure  => enabled,
    require => Package['chocolatey-agent'],
  }

  chocolateyfeature {'useChocolateyCentralManagementDeployments':
    ensure  => enabled,
    require => Package['chocolatey-agent'],
  }
}

Need Help? View our docs or file an issue.

There is already a version of this package in your Script Builder

Current Version	New Version

Downloads:

7,357,307

Downloads of v 20.12.2:

556

Last Update:

25 Apr 2024

Package Maintainer(s):

chocolatey-community

Software Author(s):

Node.js Foundation

Tags:

nodejs node javascript npm admin foss cross-platform

Node JS (Install)

This is not the latest version of Node JS (Install) available.

20.12.2 | Updated: 25 Apr 2024

Downloads:

7,357,307

Downloads of v 20.12.2:

556

Maintainer(s):

chocolatey-community

Software Author(s):

Node.js Foundation

Tags:

nodejs node javascript npm admin foss cross-platform

Node JS (Install) 20.12.2

This is not the latest version of Node JS (Install) available.

All Checks are Passing

3 Passing Tests

Show Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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

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

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

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

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

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the package:
  Download
- Follow manual internalization instructions

Package Internalizer (C4B)

Run: (additional options)

choco download nodejs.install --internalize --version=20.12.2 --source=https://community.chocolatey.org/api/v2/

For package and dependencies run:

choco push --source="'INTERNAL REPO URL'"

Automate package internalization

3. Copy Your Script

choco upgrade nodejs.install -y --source="'INTERNAL REPO URL'" --version="'20.12.2'" [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.install -y --source="'INTERNAL REPO URL'" --version="'20.12.2'" 
$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.install
  win_chocolatey:
    name: nodejs.install
    version: '20.12.2'
    source: INTERNAL REPO URL
    state: present

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


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

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


cChocoPackageInstaller nodejs.install
{
    Name     = "nodejs.install"
    Version  = "20.12.2"
    Source   = "INTERNAL REPO URL"
}

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


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

NOTE

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.

Package Approved

This package was approved as a trusted package on 25 Apr 2024.

Description

Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient. Node.js' package ecosystem, npm, is the largest ecosystem of open source libraries in the world.

This package runs the official Node JS installer, resulting in Node.exe and NPM being installed under Program Files, and added to the SYSTEM PATH environment variable.

Notes

While this package now provides both Current and LTS releases of Node.js, it is still recommended to use the nodejs-lts package if only targeting the latest LTS release is required.
If the package is out of date please check Version History for the latest submitted version. If you have a question, please ask it in Chocolatey Community Package Discussions or raise an issue on the Chocolatey Community Packages Repository if you have problems with the package. Disqus comments will generally not be responded to.

Files

legal\LICENSE.txt

Node.js is licensed for use as follows:

"""
Copyright Node.js contributors. All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to
deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
IN THE SOFTWARE.
"""

This license applies to parts of Node.js originating from the
https://github.com/joyent/node repository:

"""
Copyright Joyent, Inc. and other Node contributors. All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to
deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
IN THE SOFTWARE.
"""

The Node.js license applies to all parts of Node.js that are not externally
maintained libraries.

The externally maintained libraries used by Node.js are:

- c-ares, located at deps/cares, is licensed as follows:
  """
    Copyright 1998 by the Massachusetts Institute of Technology.
    Copyright (C) 2007-2013 by Daniel Stenberg

    Permission to use, copy, modify, and distribute this
    software and its documentation for any purpose and without
    fee is hereby granted, provided that the above copyright
    notice appear in all copies and that both that copyright
    notice and this permission notice appear in supporting
    documentation, and that the name of M.I.T. not be used in
    advertising or publicity pertaining to distribution of the
    software without specific, written prior permission.
    M.I.T. makes no representations about the suitability of
    this software for any purpose.  It is provided "as is"
    without express or implied warranty.
  """

- HTTP Parser, located at deps/http_parser, is licensed as follows:
  """
    http_parser.c is based on src/http/ngx_http_parse.c from NGINX copyright
    Igor Sysoev.

    Additional changes are licensed under the same terms as NGINX and
    copyright Joyent, Inc. and other Node contributors. All rights reserved.

    Permission is hereby granted, free of charge, to any person obtaining a copy
    of this software and associated documentation files (the "Software"), to
    deal in the Software without restriction, including without limitation the
    rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
    sell copies of the Software, and to permit persons to whom the Software is
    furnished to do so, subject to the following conditions:

    The above copyright notice and this permission notice shall be included in
    all copies or substantial portions of the Software.

    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
    FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
    IN THE SOFTWARE.
  """

- ICU, located at deps/icu-small, is licensed as follows:
  """
    COPYRIGHT AND PERMISSION NOTICE (ICU 58 and later)

    Copyright © 1991-2016 Unicode, Inc. All rights reserved.
    Distributed under the Terms of Use in http://www.unicode.org/copyright.html

    Permission is hereby granted, free of charge, to any person obtaining
    a copy of the Unicode data files and any associated documentation
    (the "Data Files") or Unicode software and any associated documentation
    (the "Software") to deal in the Data Files or Software
    without restriction, including without limitation the rights to use,
    copy, modify, merge, publish, distribute, and/or sell copies of
    the Data Files or Software, and to permit persons to whom the Data Files
    or Software are furnished to do so, provided that either
    (a) this copyright and permission notice appear with all copies
    of the Data Files or Software, or
    (b) this copyright and permission notice appear in associated
    Documentation.

    THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF
    ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
    WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
    NONINFRINGEMENT OF THIRD PARTY RIGHTS.
    IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS
    NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL
    DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
    DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
    TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
    PERFORMANCE OF THE DATA FILES OR SOFTWARE.

    Except as contained in this notice, the name of a copyright holder
    shall not be used in advertising or otherwise to promote the sale,
    use or other dealings in these Data Files or Software without prior
    written authorization of the copyright holder.

    ---------------------

    Third-Party Software Licenses

    This section contains third-party software notices and/or additional
    terms for licensed third-party software components included within ICU
    libraries.

    1. ICU License - ICU 1.8.1 to ICU 57.1

    COPYRIGHT AND PERMISSION NOTICE

    Copyright (c) 1995-2016 International Business Machines Corporation and others
    All rights reserved.

    Permission is hereby granted, free of charge, to any person obtaining
    a copy of this software and associated documentation files (the
    "Software"), to deal in the Software without restriction, including
    without limitation the rights to use, copy, modify, merge, publish,
    distribute, and/or sell copies of the Software, and to permit persons
    to whom the Software is furnished to do so, provided that the above
    copyright notice(s) and this permission notice appear in all copies of
    the Software and that both the above copyright notice(s) and this
    permission notice appear in supporting documentation.

    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
    EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
    MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
    OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
    HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY
    SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER
    RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
    CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
    CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

    Except as contained in this notice, the name of a copyright holder
    shall not be used in advertising or otherwise to promote the sale, use
    or other dealings in this Software without prior written authorization
    of the copyright holder.

    All trademarks and registered trademarks mentioned herein are the
    property of their respective owners.

    2. Chinese/Japanese Word Break Dictionary Data (cjdict.txt)

     #     The Google Chrome software developed by Google is licensed under
     # the BSD license. Other software included in this distribution is
     # provided under other licenses, as set forth below.
     #
     #  The BSD License
     #  http://opensource.org/licenses/bsd-license.php
     #  Copyright (C) 2006-2008, Google Inc.
     #
     #  All rights reserved.
     #
     #  Redistribution and use in source and binary forms, with or without
     # modification, are permitted provided that the following conditions are met:
     #
     #  Redistributions of source code must retain the above copyright notice,
     # this list of conditions and the following disclaimer.
     #  Redistributions in binary form must reproduce the above
     # copyright notice, this list of conditions and the following
     # disclaimer in the documentation and/or other materials provided with
     # the distribution.
     #  Neither the name of  Google Inc. nor the names of its
     # contributors may be used to endorse or promote products derived from
     # this software without specific prior written permission.
     #
     #
     #  THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
     # CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
     # INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
     # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
     # DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
     # LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
     # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
     # SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
     # BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
     # LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
     # NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
     # SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
     #
     #
     #  The word list in cjdict.txt are generated by combining three word lists
     # listed below with further processing for compound word breaking. The
     # frequency is generated with an iterative training against Google web
     # corpora.
     #
     #  * Libtabe (Chinese)
     #    - https://sourceforge.net/project/?group_id=1519
     #    - Its license terms and conditions are shown below.
     #
     #  * IPADIC (Japanese)
     #    - http://chasen.aist-nara.ac.jp/chasen/distribution.html
     #    - Its license terms and conditions are shown below.
     #
     #  ---------COPYING.libtabe ---- BEGIN--------------------
     #
     #  /*
     #   * Copyrighy (c) 1999 TaBE Project.
     #   * Copyright (c) 1999 Pai-Hsiang Hsiao.
     #   * All rights reserved.
     #   *
     #   * Redistribution and use in source and binary forms, with or without
     #   * modification, are permitted provided that the following conditions
     #   * are met:
     #   *
     #   * . Redistributions of source code must retain the above copyright
     #   *   notice, this list of conditions and the following disclaimer.
     #   * . Redistributions in binary form must reproduce the above copyright
     #   *   notice, this list of conditions and the following disclaimer in
     #   *   the documentation and/or other materials provided with the
     #   *   distribution.
     #   * . Neither the name of the TaBE Project nor the names of its
     #   *   contributors may be used to endorse or promote products derived
     #   *   from this software without specific prior written permission.
     #   *
     #   * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
     #   * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
     #   * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
     #   * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
     #   * REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
     #   * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
     #   * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
     #   * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
     #   * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
     #   * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
     #   * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
     #   * OF THE POSSIBILITY OF SUCH DAMAGE.
     #   */
     #
     #  /*
     #   * Copyright (c) 1999 Computer Systems and Communication Lab,
     #   *                    Institute of Information Science, Academia
     #       *                    Sinica. All rights reserved.
     #   *
     #   * Redistribution and use in source and binary forms, with or without
     #   * modification, are permitted provided that the following conditions
     #   * are met:
     #   *
     #   * . Redistributions of source code must retain the above copyright
     #   *   notice, this list of conditions and the following disclaimer.
     #   * . Redistributions in binary form must reproduce the above copyright
     #   *   notice, this list of conditions and the following disclaimer in
     #   *   the documentation and/or other materials provided with the
     #   *   distribution.
     #   * . Neither the name of the Computer Systems and Communication Lab
     #   *   nor the names of its contributors may be used to endorse or
     #   *   promote products derived from this software without specific
     #   *   prior written permission.
     #   *
     #   * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
     #   * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
     #   * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
     #   * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
     #   * REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
     #   * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
     #   * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
     #   * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
     #   * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
     #   * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
     #   * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
     #   * OF THE POSSIBILITY OF SUCH DAMAGE.
     #   */
     #
     #  Copyright 1996 Chih-Hao Tsai @ Beckman Institute,
     #      University of Illinois
     #  [email protected]  http://casper.beckman.uiuc.edu/~c-tsai4
     #
     #  ---------------COPYING.libtabe-----END--------------------------------
     #
     #
     #  ---------------COPYING.ipadic-----BEGIN-------------------------------
     #
     #  Copyright 2000, 2001, 2002, 2003 Nara Institute of Science
     #  and Technology.  All Rights Reserved.
     #
     #  Use, reproduction, and distribution of this software is permitted.
     #  Any copy of this software, whether in its original form or modified,
     #  must include both the above copyright notice and the following
     #  paragraphs.
     #
     #  Nara Institute of Science and Technology (NAIST),
     #  the copyright holders, disclaims all warranties with regard to this
     #  software, including all implied warranties of merchantability and
     #  fitness, in no event shall NAIST be liable for
     #  any special, indirect or consequential damages or any damages
     #  whatsoever resulting from loss of use, data or profits, whether in an
     #  action of contract, negligence or other tortuous action, arising out
     #  of or in connection with the use or performance of this software.
     #
     #  A large portion of the dictionary entries
     #  originate from ICOT Free Software.  The following conditions for ICOT
     #  Free Software applies to the current dictionary as well.
     #
     #  Each User may also freely distribute the Program, whether in its
     #  original form or modified, to any third party or parties, PROVIDED
     #  that the provisions of Section 3 ("NO WARRANTY") will ALWAYS appear
     #  on, or be attached to, the Program, which is distributed substantially
     #  in the same form as set out herein and that such intended
     #  distribution, if actually made, will neither violate or otherwise
     #  contravene any of the laws and regulations of the countries having
     #  jurisdiction over the User or the intended distribution itself.
     #
     #  NO WARRANTY
     #
     #  The program was produced on an experimental basis in the course of the
     #  research and development conducted during the project and is provided
     #  to users as so produced on an experimental basis.  Accordingly, the
     #  program is provided without any warranty whatsoever, whether express,
     #  implied, statutory or otherwise.  The term "warranty" used herein
     #  includes, but is not limited to, any warranty of the quality,
     #  performance, merchantability and fitness for a particular purpose of
     #  the program and the nonexistence of any infringement or violation of
     #  any right of any third party.
     #
     #  Each user of the program will agree and understand, and be deemed to
     #  have agreed and understood, that there is no warranty whatsoever for
     #  the program and, accordingly, the entire risk arising from or
     #  otherwise connected with the program is assumed by the user.
     #
     #  Therefore, neither ICOT, the copyright holder, or any other
     #  organization that participated in or was otherwise related to the
     #  development of the program and their respective officials, directors,
     #  officers and other employees shall be held liable for any and all
     #  damages, including, without limitation, general, special, incidental
     #  and consequential damages, arising out of or otherwise in connection
     #  with the use or inability to use the program or any product, material
     #  or result produced or otherwise obtained by using the program,
     #  regardless of whether they have been advised of, or otherwise had
     #  knowledge of, the possibility of such damages at any time during the
     #  project or thereafter.  Each user will be deemed to have agreed to the
     #  foregoing by his or her commencement of use of the program.  The term
     #  "use" as used herein includes, but is not limited to, the use,
     #  modification, copying and distribution of the program and the
     #  production of secondary products from the program.
     #
     #  In the case where the program, whether in its original form or
     #  modified, was distributed or delivered to or received by a user from
     #  any person, organization or entity other than ICOT, unless it makes or
     #  grants independently of ICOT any specific warranty to the user in
     #  writing, such person, organization or entity, will also be exempted
     #  from and not be held liable to the user for any such damages as noted
     #  above as far as the program is concerned.
     #
     #  ---------------COPYING.ipadic-----END----------------------------------

    3. Lao Word Break Dictionary Data (laodict.txt)

     #  Copyright (c) 2013 International Business Machines Corporation
     #  and others. All Rights Reserved.
     #
     # Project: http://code.google.com/p/lao-dictionary/
     # Dictionary: http://lao-dictionary.googlecode.com/git/Lao-Dictionary.txt
     # License: http://lao-dictionary.googlecode.com/git/Lao-Dictionary-LICENSE.txt
     #              (copied below)
     #
     #  This file is derived from the above dictionary, with slight
     #  modifications.
     #  ----------------------------------------------------------------------
     #  Copyright (C) 2013 Brian Eugene Wilson, Robert Martin Campbell.
     #  All rights reserved.
     #
     #  Redistribution and use in source and binary forms, with or without
     #  modification,
     #  are permitted provided that the following conditions are met:
     #
     #
     # Redistributions of source code must retain the above copyright notice, this
     #  list of conditions and the following disclaimer. Redistributions in
     #  binary form must reproduce the above copyright notice, this list of
     #  conditions and the following disclaimer in the documentation and/or
     #  other materials provided with the distribution.
     #
     #
     # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
     # "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
     # LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
     # FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
     # COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
     # INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
     # (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
     # SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
     # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
     # STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
     # ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
     # OF THE POSSIBILITY OF SUCH DAMAGE.
     #  --------------------------------------------------------------------------

    4. Burmese Word Break Dictionary Data (burmesedict.txt)

     #  Copyright (c) 2014 International Business Machines Corporation
     #  and others. All Rights Reserved.
     #
     #  This list is part of a project hosted at:
     #    github.com/kanyawtech/myanmar-karen-word-lists
     #
     #  --------------------------------------------------------------------------
     #  Copyright (c) 2013, LeRoy Benjamin Sharon
     #  All rights reserved.
     #
     #  Redistribution and use in source and binary forms, with or without
     #  modification, are permitted provided that the following conditions
     #  are met: Redistributions of source code must retain the above
     #  copyright notice, this list of conditions and the following
     #  disclaimer.  Redistributions in binary form must reproduce the
     #  above copyright notice, this list of conditions and the following
     #  disclaimer in the documentation and/or other materials provided
     #  with the distribution.
     #
     #    Neither the name Myanmar Karen Word Lists, nor the names of its
     #    contributors may be used to endorse or promote products derived
     #    from this software without specific prior written permission.
     #
     #  THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
     #  CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
     #  INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
     #  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
     #  DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS
     #  BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
     #  EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
     #  TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
     #  DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
     #  ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
     #  TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
     #  THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
     #  SUCH DAMAGE.
     #  --------------------------------------------------------------------------

    5. Time Zone Database

      ICU uses the public domain data and code derived from Time Zone
    Database for its time zone support. The ownership of the TZ database
    is explained in BCP 175: Procedure for Maintaining the Time Zone
    Database section 7.

     # 7.  Database Ownership
     #
     #    The TZ database itself is not an IETF Contribution or an IETF
     #    document.  Rather it is a pre-existing and regularly updated work
     #    that is in the public domain, and is intended to remain in the
     #    public domain.  Therefore, BCPs 78 [RFC5378] and 79 [RFC3979] do
     #    not apply to the TZ Database or contributions that individuals make
     #    to it.  Should any claims be made and substantiated against the TZ
     #    Database, the organization that is providing the IANA
     #    Considerations defined in this RFC, under the memorandum of
     #    understanding with the IETF, currently ICANN, may act in accordance
     #    with all competent court orders.  No ownership claims will be made
     #    by ICANN or the IETF Trust on the database or the code.  Any person
     #    making a contribution to the database or code waives all rights to
     #    future claims in that contribution or in the TZ Database.
  """

- libuv, located at deps/uv, is licensed as follows:
  """
    libuv is part of the Node project: http://nodejs.org/
    libuv may be distributed alone under Node's license:

    ====

    Copyright Joyent, Inc. and other Node contributors. All rights reserved.
    Permission is hereby granted, free of charge, to any person obtaining a copy
    of this software and associated documentation files (the "Software"), to
    deal in the Software without restriction, including without limitation the
    rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
    sell copies of the Software, and to permit persons to whom the Software is
    furnished to do so, subject to the following conditions:

    The above copyright notice and this permission notice shall be included in
    all copies or substantial portions of the Software.

    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
    FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
    IN THE SOFTWARE.

    ====

    This license applies to all parts of libuv that are not externally
    maintained libraries.

    The externally maintained libraries used by libuv are:

      - tree.h (from FreeBSD), copyright Niels Provos. Two clause BSD license.

      - inet_pton and inet_ntop implementations, contained in src/inet.c, are
        copyright the Internet Systems Consortium, Inc., and licensed under the ISC
        license.

      - stdint-msvc2008.h (from msinttypes), copyright Alexander Chemeris. Three
        clause BSD license.

      - pthread-fixes.h, pthread-fixes.c, copyright Google Inc. and Sony Mobile
        Communications AB. Three clause BSD license.

      - android-ifaddrs.h, android-ifaddrs.c, copyright Berkeley Software Design
        Inc, Kenneth MacKay and Emergya (Cloud4all, FP7/2007-2013, grant agreement
        n° 289016). Three clause BSD license.
  """

- OpenSSL, located at deps/openssl, is licensed as follows:
  """
    Copyright (c) 1998-2016 The OpenSSL Project.  All rights reserved.

    Redistribution and use in source and binary forms, with or without
    modification, are permitted provided that the following conditions
    are met:

    1. Redistributions of source code must retain the above copyright
    notice, this list of conditions and the following disclaimer.

    2. Redistributions in binary form must reproduce the above copyright
    notice, this list of conditions and the following disclaimer in
    the documentation and/or other materials provided with the
    distribution.

    3. All advertising materials mentioning features or use of this
    software must display the following acknowledgment:
    "This product includes software developed by the OpenSSL Project
    for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

    4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
    endorse or promote products derived from this software without
    prior written permission. For written permission, please contact
    [email protected].

    5. Products derived from this software may not be called "OpenSSL"
    nor may "OpenSSL" appear in their names without prior written
    permission of the OpenSSL Project.

    6. Redistributions of any form whatsoever must retain the following
    acknowledgment:
    "This product includes software developed by the OpenSSL Project
    for use in the OpenSSL Toolkit (http://www.openssl.org/)"

    THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
    EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
    IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
    PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE OpenSSL PROJECT OR
    ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
    NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
    LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
    HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
    STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
    ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
    OF THE POSSIBILITY OF SUCH DAMAGE.
    ====================================================================

    This product includes cryptographic software written by Eric Young
    ([email protected]).  This product includes software written by Tim
    Hudson ([email protected]).
  """

- Punycode.js, located at lib/punycode.js, is licensed as follows:
  """
    Copyright Mathias Bynens <https://mathiasbynens.be/>

    Permission is hereby granted, free of charge, to any person obtaining
    a copy of this software and associated documentation files (the
    "Software"), to deal in the Software without restriction, including
    without limitation the rights to use, copy, modify, merge, publish,
    distribute, sublicense, and/or sell copies of the Software, and to
    permit persons to whom the Software is furnished to do so, subject to
    the following conditions:

    The above copyright notice and this permission notice shall be
    included in all copies or substantial portions of the Software.

    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
    EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
    MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
    NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
    LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
    OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
    WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
  """

- V8, located at deps/v8, is licensed as follows:
  """
    This license applies to all parts of V8 that are not externally
    maintained libraries.  The externally maintained libraries used by V8
    are:

      - PCRE test suite, located in
        test/mjsunit/third_party/regexp-pcre/regexp-pcre.js.  This is based on the
        test suite from PCRE-7.3, which is copyrighted by the University
        of Cambridge and Google, Inc.  The copyright notice and license
        are embedded in regexp-pcre.js.

      - Layout tests, located in test/mjsunit/third_party/object-keys.  These are
        based on layout tests from webkit.org which are copyrighted by
        Apple Computer, Inc. and released under a 3-clause BSD license.

      - Strongtalk assembler, the basis of the files assembler-arm-inl.h,
        assembler-arm.cc, assembler-arm.h, assembler-ia32-inl.h,
        assembler-ia32.cc, assembler-ia32.h, assembler-x64-inl.h,
        assembler-x64.cc, assembler-x64.h, assembler-mips-inl.h,
        assembler-mips.cc, assembler-mips.h, assembler.cc and assembler.h.
        This code is copyrighted by Sun Microsystems Inc. and released
        under a 3-clause BSD license.

      - Valgrind client API header, located at third_party/valgrind/valgrind.h
        This is release under the BSD license.

    These libraries have their own licenses; we recommend you read them,
    as their terms may differ from the terms below.

    Further license information can be found in LICENSE files located in
    sub-directories.

    Copyright 2014, the V8 project authors. All rights reserved.
    Redistribution and use in source and binary forms, with or without
    modification, are permitted provided that the following conditions are
    met:

        * Redistributions of source code must retain the above copyright
          notice, this list of conditions and the following disclaimer.
        * Redistributions in binary form must reproduce the above
          copyright notice, this list of conditions and the following
          disclaimer in the documentation and/or other materials provided
          with the distribution.
        * Neither the name of Google Inc. nor the names of its
          contributors may be used to endorse or promote products derived
          from this software without specific prior written permission.

    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
    "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
    LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
    A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
    OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
    LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
    DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
    THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
    (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
    OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  """

- zlib, located at deps/zlib, is licensed as follows:
  """
    zlib.h -- interface of the 'zlib' general purpose compression library
    version 1.2.8, April 28th, 2013

    Copyright (C) 1995-2013 Jean-loup Gailly and Mark Adler

    This software is provided 'as-is', without any express or implied
    warranty.  In no event will the authors be held liable for any damages
    arising from the use of this software.

    Permission is granted to anyone to use this software for any purpose,
    including commercial applications, and to alter it and redistribute it
    freely, subject to the following restrictions:

    1. The origin of this software must not be misrepresented; you must not
    claim that you wrote the original software. If you use this software
    in a product, an acknowledgment in the product documentation would be
    appreciated but is not required.
    2. Altered source versions must be plainly marked as such, and must not be
    misrepresented as being the original software.
    3. This notice may not be removed or altered from any source distribution.

    Jean-loup Gailly        Mark Adler
    [email protected]          [email protected]
  """

- npm, located at deps/npm, is licensed as follows:
  """
    The npm application
    Copyright (c) npm, Inc. and Contributors
    Licensed on the terms of The Artistic License 2.0

    Node package dependencies of the npm application
    Copyright (c) their respective copyright owners
    Licensed on their respective license terms

    The npm public registry at https://registry.npmjs.org
    and the npm website at https://www.npmjs.com
    Operated by npm, Inc.
    Use governed by terms published on https://www.npmjs.com

    "Node.js"
    Trademark Joyent, Inc., https://joyent.com
    Neither npm nor npm, Inc. are affiliated with Joyent, Inc.

    The Node.js application
    Project of Node Foundation, https://nodejs.org

    The npm Logo
    Copyright (c) Mathias Pettersson and Brian Hammond

    "Gubblebum Blocky" typeface
    Copyright (c) Tjarda Koster, https://jelloween.deviantart.com
    Used with permission

    --------

    The Artistic License 2.0

    Copyright (c) 2000-2006, The Perl Foundation.

    Everyone is permitted to copy and distribute verbatim copies
    of this license document, but changing it is not allowed.

    Preamble

    This license establishes the terms under which a given free software
    Package may be copied, modified, distributed, and/or redistributed.
    The intent is that the Copyright Holder maintains some artistic
    control over the development of that Package while still keeping the
    Package available as open source and free software.

    You are always permitted to make arrangements wholly outside of this
    license directly with the Copyright Holder of a given Package.  If the
    terms of this license do not permit the full use that you propose to
    make of the Package, you should contact the Copyright Holder and seek
    a different licensing arrangement.

    Definitions

        "Copyright Holder" means the individual(s) or organization(s)
        named in the copyright notice for the entire Package.

        "Contributor" means any party that has contributed code or other
        material to the Package, in accordance with the Copyright Holder's
        procedures.

        "You" and "your" means any person who would like to copy,
        distribute, or modify the Package.

        "Package" means the collection of files distributed by the
        Copyright Holder, and derivatives of that collection and/or of
        those files. A given Package may consist of either the Standard
        Version, or a Modified Version.

        "Distribute" means providing a copy of the Package or making it
        accessible to anyone else, or in the case of a company or
        organization, to others outside of your company or organization.

        "Distributor Fee" means any fee that you charge for Distributing
        this Package or providing support for this Package to another
        party.  It does not mean licensing fees.

        "Standard Version" refers to the Package if it has not been
        modified, or has been modified only in ways explicitly requested
        by the Copyright Holder.

        "Modified Version" means the Package, if it has been changed, and
        such changes were not explicitly requested by the Copyright
        Holder.

        "Original License" means this Artistic License as Distributed with
        the Standard Version of the Package, in its current version or as
        it may be modified by The Perl Foundation in the future.

        "Source" form means the source code, documentation source, and
        configuration files for the Package.

        "Compiled" form means the compiled bytecode, object code, binary,
        or any other form resulting from mechanical transformation or
        translation of the Source form.

    Permission for Use and Modification Without Distribution

    (1)  You are permitted to use the Standard Version and create and use
    Modified Versions for any purpose without restriction, provided that
    you do not Distribute the Modified Version.

    Permissions for Redistribution of the Standard Version

    (2)  You may Distribute verbatim copies of the Source form of the
    Standard Version of this Package in any medium without restriction,
    either gratis or for a Distributor Fee, provided that you duplicate
    all of the original copyright notices and associated disclaimers.  At
    your discretion, such verbatim copies may or may not include a
    Compiled form of the Package.

    (3)  You may apply any bug fixes, portability changes, and other
    modifications made available from the Copyright Holder.  The resulting
    Package will still be considered the Standard Version, and as such
    will be subject to the Original License.

    Distribution of Modified Versions of the Package as Source

    (4)  You may Distribute your Modified Version as Source (either gratis
    or for a Distributor Fee, and with or without a Compiled form of the
    Modified Version) provided that you clearly document how it differs
    from the Standard Version, including, but not limited to, documenting
    any non-standard features, executables, or modules, and provided that
    you do at least ONE of the following:

        (a)  make the Modified Version available to the Copyright Holder
        of the Standard Version, under the Original License, so that the
        Copyright Holder may include your modifications in the Standard
        Version.

        (b)  ensure that installation of your Modified Version does not
        prevent the user installing or running the Standard Version. In
        addition, the Modified Version must bear a name that is different
        from the name of the Standard Version.

        (c)  allow anyone who receives a copy of the Modified Version to
        make the Source form of the Modified Version available to others
        under

            (i)  the Original License or

            (ii)  a license that permits the licensee to freely copy,
            modify and redistribute the Modified Version using the same
            licensing terms that apply to the copy that the licensee
            received, and requires that the Source form of the Modified
            Version, and of any works derived from it, be made freely
            available in that license fees are prohibited but Distributor
            Fees are allowed.

    Distribution of Compiled Forms of the Standard Version
    or Modified Versions without the Source

    (5)  You may Distribute Compiled forms of the Standard Version without
    the Source, provided that you include complete instructions on how to
    get the Source of the Standard Version.  Such instructions must be
    valid at the time of your distribution.  If these instructions, at any
    time while you are carrying out such distribution, become invalid, you
    must provide new instructions on demand or cease further distribution.
    If you provide valid instructions or cease distribution within thirty
    days after you become aware that the instructions are invalid, then
    you do not forfeit any of your rights under this license.

    (6)  You may Distribute a Modified Version in Compiled form without
    the Source, provided that you comply with Section 4 with respect to
    the Source of the Modified Version.

    Aggregating or Linking the Package

    (7)  You may aggregate the Package (either the Standard Version or
    Modified Version) with other packages and Distribute the resulting
    aggregation provided that you do not charge a licensing fee for the
    Package.  Distributor Fees are permitted, and licensing fees for other
    components in the aggregation are permitted. The terms of this license
    apply to the use and Distribution of the Standard or Modified Versions
    as included in the aggregation.

    (8) You are permitted to link Modified and Standard Versions with
    other works, to embed the Package in a larger work of your own, or to
    build stand-alone binary or bytecode versions of applications that
    include the Package, and Distribute the result without restriction,
    provided the result does not expose a direct interface to the Package.

    Items That are Not Considered Part of a Modified Version

    (9) Works (including, but not limited to, modules and scripts) that
    merely extend or make use of the Package, do not, by themselves, cause
    the Package to be a Modified Version.  In addition, such works are not
    considered parts of the Package itself, and are not subject to the
    terms of this license.

    General Provisions

    (10)  Any use, modification, and distribution of the Standard or
    Modified Versions is governed by this Artistic License. By using,
    modifying or distributing the Package, you accept this license. Do not
    use, modify, or distribute the Package, if you do not accept this
    license.

    (11)  If your Modified Version has been derived from a Modified
    Version made by someone other than you, you are nevertheless required
    to ensure that your Modified Version complies with the requirements of
    this license.

    (12)  This license does not grant you the right to use any trademark,
    service mark, tradename, or logo of the Copyright Holder.

    (13)  This license includes the non-exclusive, worldwide,
    free-of-charge patent license to make, have made, use, offer to sell,
    sell, import and otherwise transfer the Package with respect to any
    patent claims licensable by the Copyright Holder that are necessarily
    infringed by the Package. If you institute patent litigation
    (including a cross-claim or counterclaim) against any party alleging
    that the Package constitutes direct or contributory patent
    infringement, then this Artistic License to you shall terminate on the
    date that such litigation is filed.

    (14)  Disclaimer of Warranty:
    THE PACKAGE IS PROVIDED BY THE COPYRIGHT HOLDER AND CONTRIBUTORS "AS
    IS' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES. THE IMPLIED
    WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
    NON-INFRINGEMENT ARE DISCLAIMED TO THE EXTENT PERMITTED BY YOUR LOCAL
    LAW. UNLESS REQUIRED BY LAW, NO COPYRIGHT HOLDER OR CONTRIBUTOR WILL
    BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
    DAMAGES ARISING IN ANY WAY OUT OF THE USE OF THE PACKAGE, EVEN IF
    ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

    --------
  """

- GYP, located at tools/gyp, is licensed as follows:
  """
    Copyright (c) 2009 Google Inc. All rights reserved.

    Redistribution and use in source and binary forms, with or without
    modification, are permitted provided that the following conditions are
    met:

       * Redistributions of source code must retain the above copyright
    notice, this list of conditions and the following disclaimer.
       * Redistributions in binary form must reproduce the above
    copyright notice, this list of conditions and the following disclaimer
    in the documentation and/or other materials provided with the
    distribution.
       * Neither the name of Google Inc. nor the names of its
    contributors may be used to endorse or promote products derived from
    this software without specific prior written permission.

    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
    "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
    LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
    A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
    OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
    LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
    DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
    THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
    (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
    OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  """

- marked, located at tools/doc/node_modules/marked, is licensed as follows:
  """
    Copyright (c) 2011-2014, Christopher Jeffrey (https://github.com/chjj/)

    Permission is hereby granted, free of charge, to any person obtaining a copy
    of this software and associated documentation files (the "Software"), to deal
    in the Software without restriction, including without limitation the rights
    to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
    copies of the Software, and to permit persons to whom the Software is
    furnished to do so, subject to the following conditions:

    The above copyright notice and this permission notice shall be included in
    all copies or substantial portions of the Software.

    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
    OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
    THE SOFTWARE.
  """

- cpplint.py, located at tools/cpplint.py, is licensed as follows:
  """
    Copyright (c) 2009 Google Inc. All rights reserved.

    Redistribution and use in source and binary forms, with or without
    modification, are permitted provided that the following conditions are
    met:

       * Redistributions of source code must retain the above copyright
    notice, this list of conditions and the following disclaimer.
       * Redistributions in binary form must reproduce the above
    copyright notice, this list of conditions and the following disclaimer
    in the documentation and/or other materials provided with the
    distribution.
       * Neither the name of Google Inc. nor the names of its
    contributors may be used to endorse or promote products derived from
    this software without specific prior written permission.

    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
    "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
    LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
    A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
    OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
    LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
    DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
    THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
    (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
    OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  """

- ESLint, located at tools/eslint, is licensed as follows:
  """
    ESLint
    Copyright jQuery Foundation and other contributors, https://jquery.org/

    Permission is hereby granted, free of charge, to any person obtaining a copy
    of this software and associated documentation files (the "Software"), to deal
    in the Software without restriction, including without limitation the rights
    to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
    copies of the Software, and to permit persons to whom the Software is
    furnished to do so, subject to the following conditions:

    The above copyright notice and this permission notice shall be included in
    all copies or substantial portions of the Software.

    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
    OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
    THE SOFTWARE.
  """

- gtest, located at deps/gtest, is licensed as follows:
  """
    Copyright 2008, Google Inc.
    All rights reserved.

    Redistribution and use in source and binary forms, with or without
    modification, are permitted provided that the following conditions are
    met:

        * Redistributions of source code must retain the above copyright
    notice, this list of conditions and the following disclaimer.
        * Redistributions in binary form must reproduce the above
    copyright notice, this list of conditions and the following disclaimer
    in the documentation and/or other materials provided with the
    distribution.
        * Neither the name of Google Inc. nor the names of its
    contributors may be used to endorse or promote products derived from
    this software without specific prior written permission.

    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
    "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
    LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
    A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
    OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
    LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
    DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
    THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
    (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
    OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  """

- node-weak, located at test/gc/node_modules/weak, is licensed as follows:
  """
    Copyright (c) 2011, Ben Noordhuis <[email protected]>

    Permission to use, copy, modify, and/or distribute this software for any
    purpose with or without fee is hereby granted, provided that the above
    copyright notice and this permission notice appear in all copies.

    THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
    WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
    MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
    ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
    WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
    ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
    OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
  """

- v8_inspector, located at deps/v8_inspector/third_party/v8_inspector, is licensed as follows:
  """
    // Copyright 2015 The Chromium Authors. All rights reserved.
    //
    // Redistribution and use in source and binary forms, with or without
    // modification, are permitted provided that the following conditions are
    // met:
    //
    //    * Redistributions of source code must retain the above copyright
    // notice, this list of conditions and the following disclaimer.
    //    * Redistributions in binary form must reproduce the above
    // copyright notice, this list of conditions and the following disclaimer
    // in the documentation and/or other materials provided with the
    // distribution.
    //    * Neither the name of Google Inc. nor the names of its
    // contributors may be used to endorse or promote products derived from
    // this software without specific prior written permission.
    //
    // THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
    // "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
    // LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
    // A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
    // OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    // SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
    // LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
    // DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
    // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
    // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
    // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  """

- jinja2, located at deps/v8_inspector/third_party/jinja2, is licensed as follows:
  """
    Copyright (c) 2009 by the Jinja Team, see AUTHORS for more details.
    
    Some rights reserved.
    
    Redistribution and use in source and binary forms, with or without
    modification, are permitted provided that the following conditions are
    met:
    
        * Redistributions of source code must retain the above copyright
          notice, this list of conditions and the following disclaimer.
    
        * Redistributions in binary form must reproduce the above
          copyright notice, this list of conditions and the following
          disclaimer in the documentation and/or other materials provided
          with the distribution.
    
        * The names of the contributors may not be used to endorse or
          promote products derived from this software without specific
          prior written permission.
    
    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
    "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
    LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
    A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
    OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
    LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
    DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
    THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
    (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
    OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  """

- markupsafe, located at deps/v8_inspector/third_party/markupsafe, is licensed as follows:
  """
    Copyright (c) 2010 by Armin Ronacher and contributors.  See AUTHORS
    for more details.

    Some rights reserved.

    Redistribution and use in source and binary forms of the software as well
    as documentation, with or without modification, are permitted provided
    that the following conditions are met:

    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.

    * Redistributions in binary form must reproduce the above
      copyright notice, this list of conditions and the following
      disclaimer in the documentation and/or other materials provided
      with the distribution.

    * The names of the contributors may not be used to endorse or
      promote products derived from this software without specific
      prior written permission.

    THIS SOFTWARE AND DOCUMENTATION IS PROVIDED BY THE COPYRIGHT HOLDERS AND
    CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
    NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
    A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
    OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
    EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
    PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
    PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
    LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
    NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
    SOFTWARE AND DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
    DAMAGE.
  """

legal\VERIFICATION.txt

VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The installer has been downloaded from GitHub and can be verified like this:

1. Download the following installers:
  32-Bit: <https://nodejs.org/dist/v20.12.2/node-v20.12.2-x86.msi>
  64-Bit: <https://nodejs.org/dist/v20.12.2/node-v20.12.2-x64.msi>
2. You can use one of the following methods to obtain the checksum
  - Use powershell function 'Get-Filehash'
  - Use chocolatey utility 'checksum.exe'

  checksum type: sha256
  checksum32: 2655083616F0AFC6C7A619069506614C4EF32C12BC31B5C455FE1E4815F03D23
  checksum64: 20C578361911D7B0CF153B293B025970ECA383A2C802E0DF438AC254AACA165D

File 'LICENSE.txt' is obtained from <https://github.com/nodejs/node/blob/03023fa7ae060c082a014f792d5d1f481a599460/LICENSE>

tools\chocolateyInstall.ps1

$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path $MyInvocation.MyCommand.Definition

$filePath32 = "$toolsPath\node-v20.12.2-x86.msi"
$filePath64 = "$toolsPath\node-v20.12.2-x64.msi"
$installFile = if ((Get-OSArchitectureWidth 64) -and $env:chocolateyForceX86 -ne 'true') {
                      Write-Host "Installing 64 bit version"; $filePath64 }
               else { Write-Host "Installing 32 bit version"; $filePath32 }

$packageArgs = @{
  PackageName    = 'nodejs.install'
  FileType       = 'msi'
  SoftwareName   = 'Node.js'
  File           = $installFile
  SilentArgs     = '/quiet ADDLOCAL=ALL'
  ValidExitCodes = @(0)
}
Install-ChocolateyInstallPackage @packageArgs

Remove-Item -Force $filePath32, $filePath64 -ea 0

tools\node-v20.12.2-x64.msi

md5: 0DF081AA47E7159E585488A161A97466 | sha1: 2DC9A592DBB208624AFF11A57F97BEA89A315973 | sha256: 20C578361911D7B0CF153B293B025970ECA383A2C802E0DF438AC254AACA165D | sha512: 2E1B58ADD6A714281F2DDEB936069C0EB8CE24AE2E440941379C4273AFD7F1A96B162D5B88211E8678804BAD652E48C99A4993E0E0D0DA4D1ABD7550D397E836

tools\node-v20.12.2-x86.msi

md5: 5D8EC597DE43A9D8C025359E50D70440 | sha1: DC0BD543069DC1848B1CB3DDDC4C450AFCDB04EC | sha256: 2655083616F0AFC6C7A619069506614C4EF32C12BC31B5C455FE1E4815F03D23 | sha512: 58FCD04CCF8DCA58651CDA71233C99B97CBCCCE0E8D371E55B0FB5698C185CFA94FBC53916FA026B6D4AB153428A13E8B369C824B6822639D5A0FF43E9A18312

Virus Scan Results

node-v20.12.2-x64.msi (20c578361911) - ## / 61
nodejs.install.20.12.2.nupkg (7e7ab8d411a4) - ## / 57
node-v20.12.2-x86.msi (2655083616f0) - ## / 60

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 History

Version	Downloads	Last Updated	Status
Node JS (Install) 22.2.0	389	Thursday, May 16, 2024	Approved
Node JS (Install) 22.1.0	21831	Thursday, May 2, 2024	Approved
Node JS (Install) 22.0.0	15691	Thursday, April 25, 2024	Approved
Node JS (Install) 21.7.3	245	Thursday, April 25, 2024	Approved
Node JS (Install) 21.7.1	59706	Saturday, March 9, 2024	Approved
Node JS (Install) 21.7.0	6029	Thursday, March 7, 2024	Approved
Node JS (Install) 21.6.2	39061	Thursday, February 15, 2024	Approved
Node JS (Install) 21.6.1	42987	Tuesday, January 23, 2024	Approved
Node JS (Install) 21.6.0	15736	Monday, January 15, 2024	Approved
Node JS (Install) 21.5.0	14385	Wednesday, December 20, 2023	Approved
Node JS (Install) 21.4.0	82285	Tuesday, December 5, 2023	Approved
Node JS (Install) 21.3.0	12316	Friday, December 1, 2023	Approved
Node JS (Install) 21.2.0	45266	Tuesday, November 14, 2023	Approved
Node JS (Install) 21.1.0	57744	Tuesday, October 24, 2023	Approved
Node JS (Install) 21.0.0	21891	Tuesday, October 17, 2023	Approved
Node JS (Install) 20.13.1	160	Thursday, May 9, 2024	Approved
Node JS (Install) 20.13.0	55	Tuesday, May 7, 2024	Approved
Node JS (Install) 20.12.2	556	Thursday, April 25, 2024	Approved
Node JS (Install) 20.11.1	2989	Thursday, February 15, 2024	Approved
Node JS (Install) 20.11.0	1476	Wednesday, January 10, 2024	Approved
Node JS (Install) 20.10.0	3279	Wednesday, November 22, 2023	Approved
Node JS (Install) 20.9.0	1325	Tuesday, October 24, 2023	Approved
Node JS (Install) 20.8.1	12449	Saturday, October 14, 2023	Approved
Node JS (Install) 20.8.0	21454	Friday, September 29, 2023	Approved
Node JS (Install) 20.7.0	55299	Tuesday, September 19, 2023	Approved
Node JS (Install) 20.6.1	9445	Friday, September 8, 2023	Approved
Node JS (Install) 20.6.0	37974	Tuesday, September 5, 2023	Approved
Node JS (Install) 20.5.1	35773	Wednesday, August 9, 2023	Approved
Node JS (Install) 20.5.0	30777	Friday, July 21, 2023	Approved
Node JS (Install) 20.4.0	27431	Wednesday, July 5, 2023	Approved
Node JS (Install) 20.3.1	18671	Monday, June 26, 2023	Approved
Node JS (Install) 20.3.0	26404	Thursday, June 8, 2023	Approved
Node JS (Install) 20.2.0	38422	Wednesday, May 17, 2023	Approved
Node JS (Install) 20.1.0	24256	Thursday, May 4, 2023	Approved
Node JS (Install) 20.0.0	28555	Tuesday, April 18, 2023	Approved
Node JS (Install) 19.9.0	26017	Tuesday, April 11, 2023	Approved
Node JS (Install) 19.8.1	37029	Thursday, March 16, 2023	Approved
Node JS (Install) 19.8.0	5423	Wednesday, March 15, 2023	Approved
Node JS (Install) 19.7.0	34810	Wednesday, February 22, 2023	Approved
Node JS (Install) 19.6.1	3222	Friday, February 17, 2023	Approved
Node JS (Install) 19.6.0	49802	Thursday, February 2, 2023	Approved
Node JS (Install) 19.5.0	16152	Wednesday, January 25, 2023	Approved
Node JS (Install) 19.4.0	25434	Friday, January 6, 2023	Approved
Node JS (Install) 19.3.0	16032	Thursday, December 15, 2022	Approved
Node JS (Install) 19.2.0	34115	Wednesday, November 30, 2022	Approved
Node JS (Install) 19.1.0	20173	Tuesday, November 15, 2022	Approved
Node JS (Install) 19.0.0	23987	Friday, November 4, 2022	Approved
Node JS (Install) 18.20.2	1329	Thursday, April 25, 2024	Approved
Node JS (Install) 18.18.2	21991	Saturday, October 14, 2023	Approved
Node JS (Install) 18.18.1	4600	Wednesday, October 11, 2023	Approved
Node JS (Install) 18.18.0	8149	Tuesday, September 19, 2023	Approved
Node JS (Install) 18.17.1	13565	Wednesday, August 9, 2023	Approved
Node JS (Install) 18.17.0	4841	Wednesday, July 19, 2023	Approved
Node JS (Install) 18.16.1	8597	Monday, June 26, 2023	Approved
Node JS (Install) 18.16.0	13631	Thursday, April 13, 2023	Approved
Node JS (Install) 18.15.0	13447	Wednesday, March 8, 2023	Approved
Node JS (Install) 18.14.2	3068	Wednesday, February 22, 2023	Approved
Node JS (Install) 18.14.1	729	Friday, February 17, 2023	Approved
Node JS (Install) 18.14.0	644	Friday, February 3, 2023	Approved
Node JS (Install) 18.13.0	1221	Friday, January 6, 2023	Approved
Node JS (Install) 18.12.1	11388	Saturday, November 5, 2022	Approved
Node JS (Install) 18.12.0	20937	Wednesday, October 26, 2022	Approved
Node JS (Install) 18.11.0	24746	Friday, October 14, 2022	Approved
Node JS (Install) 18.10.0	31610	Wednesday, September 28, 2022	Approved
Node JS (Install) 18.9.1	10592	Friday, September 23, 2022	Approved
Node JS (Install) 18.9.0	23297	Thursday, September 8, 2022	Approved
Node JS (Install) 18.8.0	21866	Wednesday, August 24, 2022	Approved
Node JS (Install) 18.7.0	38223	Wednesday, July 27, 2022	Approved
Node JS (Install) 18.6.0	21206	Thursday, July 14, 2022	Approved
Node JS (Install) 18.5.0	12392	Thursday, July 7, 2022	Approved
Node JS (Install) 18.4.0	28653	Thursday, June 16, 2022	Approved
Node JS (Install) 18.3.0	22992	Thursday, June 2, 2022	Approved
Node JS (Install) 17.9.1	882	Thursday, June 2, 2022	Approved
Node JS (Install) 17.9.0	62792	Friday, April 8, 2022	Approved
Node JS (Install) 17.8.0	25433	Tuesday, March 22, 2022	Approved
Node JS (Install) 17.7.2	9617	Friday, March 18, 2022	Approved
Node JS (Install) 17.7.1	14124	Friday, March 11, 2022	Approved
Node JS (Install) 17.7.0	4650	Wednesday, March 9, 2022	Approved
Node JS (Install) 17.6.0	22287	Wednesday, February 23, 2022	Approved
Node JS (Install) 17.5.0	27667	Friday, February 11, 2022	Approved
Node JS (Install) 17.4.0	33904	Tuesday, January 18, 2022	Approved
Node JS (Install) 17.3.1	17370	Tuesday, January 11, 2022	Approved
Node JS (Install) 17.3.0	33291	Saturday, December 18, 2021	Approved
Node JS (Install) 17.2.0	28673	Tuesday, November 30, 2021	Approved
Node JS (Install) 17.1.0	36570	Wednesday, November 10, 2021	Approved
Node JS (Install) 17.0.1	36769	Thursday, October 21, 2021	Approved
Node JS (Install) 17.0.0	4296	Tuesday, October 19, 2021	Approved
Node JS (Install) 16.20.1	4139	Monday, June 26, 2023	Approved
Node JS (Install) 16.20.0	9804	Thursday, March 30, 2023	Approved
Node JS (Install) 16.19.1	2492	Friday, February 17, 2023	Approved
Node JS (Install) 16.19.0	7301	Tuesday, December 13, 2022	Approved
Node JS (Install) 16.18.1	10562	Friday, November 4, 2022	Approved
Node JS (Install) 16.18.0	6219	Wednesday, October 12, 2022	Approved
Node JS (Install) 16.17.1	10867	Friday, September 23, 2022	Approved
Node JS (Install) 16.17.0	11263	Tuesday, August 16, 2022	Approved
Node JS (Install) 16.16.0	20936	Thursday, July 7, 2022	Approved
Node JS (Install) 16.15.1	7037	Thursday, June 2, 2022	Approved
Node JS (Install) 16.14.2	15905	Friday, March 18, 2022	Approved
Node JS (Install) 16.14.1	450	Wednesday, March 16, 2022	Approved
Node JS (Install) 16.14.0	27881	Wednesday, February 9, 2022	Approved
Node JS (Install) 16.13.2	10592	Tuesday, January 11, 2022	Approved
Node JS (Install) 16.13.1	8683	Wednesday, December 1, 2021	Approved
Node JS (Install) 16.13.0	7877	Tuesday, October 26, 2021	Approved
Node JS (Install) 16.12.0	1282	Wednesday, October 20, 2021	Approved
Node JS (Install) 16.11.1	18400	Tuesday, October 12, 2021	Approved
Node JS (Install) 16.11.0	10433	Friday, October 8, 2021	Approved
Node JS (Install) 16.10.0	53036	Thursday, September 23, 2021	Approved
Node JS (Install) 16.9.1	37859	Saturday, September 11, 2021	Approved
Node JS (Install) 16.9.0	9390	Tuesday, September 7, 2021	Approved
Node JS (Install) 16.8.0	24345	Thursday, August 26, 2021	Approved
Node JS (Install) 16.7.0	22192	Wednesday, August 18, 2021	Approved
Node JS (Install) 16.6.2	15158	Wednesday, August 11, 2021	Approved
Node JS (Install) 16.6.1	87622	Tuesday, August 3, 2021	Approved
Node JS (Install) 16.6.0	10652	Friday, July 30, 2021	Approved
Node JS (Install) 16.5.0	31601	Wednesday, July 14, 2021	Approved
Node JS (Install) 16.4.2	20233	Monday, July 5, 2021	Approved
Node JS (Install) 16.4.1	11857	Thursday, July 1, 2021	Approved
Node JS (Install) 16.4.0	27321	Wednesday, June 23, 2021	Approved
Node JS (Install) 16.3.0	39337	Thursday, June 3, 2021	Approved
Node JS (Install) 16.2.0	34994	Wednesday, May 19, 2021	Approved
Node JS (Install) 16.1.0	30134	Tuesday, May 4, 2021	Approved
Node JS (Install) 16.0.0	33413	Tuesday, April 20, 2021	Approved
Node JS (Install) 15.14.0	34775	Wednesday, April 7, 2021	Approved
Node JS (Install) 15.13.0	12126	Wednesday, March 31, 2021	Approved
Node JS (Install) 15.12.0	32301	Thursday, March 18, 2021	Approved
Node JS (Install) 15.11.0	35095	Wednesday, March 3, 2021	Approved
Node JS (Install) 15.10.0	21486	Tuesday, February 23, 2021	Approved
Node JS (Install) 15.9.0	15167	Thursday, February 18, 2021	Approved
Node JS (Install) 15.8.0	37399	Wednesday, February 3, 2021	Approved
Node JS (Install) 15.7.0	17813	Tuesday, January 26, 2021	Approved
Node JS (Install) 15.6.0	22405	Friday, January 15, 2021	Approved
Node JS (Install) 15.5.1	32404	Tuesday, January 5, 2021	Approved
Node JS (Install) 15.5.0	24446	Wednesday, December 23, 2020	Approved
Node JS (Install) 15.4.0	29321	Wednesday, December 9, 2020	Approved
Node JS (Install) 15.3.0	37812	Tuesday, November 24, 2020	Approved
Node JS (Install) 15.2.1	17027	Monday, November 16, 2020	Approved
Node JS (Install) 15.2.0	17085	Wednesday, November 11, 2020	Approved
Node JS (Install) 15.1.0	24894	Thursday, November 5, 2020	Approved
Node JS (Install) 15.0.1	33269	Thursday, October 22, 2020	Approved
Node JS (Install) 15.0.0	6824	Tuesday, October 20, 2020	Approved
Node JS (Install) 14.21.3	3904	Friday, February 17, 2023	Approved
Node JS (Install) 14.21.2	794	Tuesday, December 13, 2022	Approved
Node JS (Install) 14.21.1	851	Friday, November 4, 2022	Approved
Node JS (Install) 14.21.0	189	Wednesday, November 2, 2022	Approved
Node JS (Install) 14.20.1	565	Friday, September 23, 2022	Approved
Node JS (Install) 14.20.0	4001	Thursday, July 7, 2022	Approved
Node JS (Install) 14.19.3	949	Thursday, June 2, 2022	Approved
Node JS (Install) 14.19.1	23554	Friday, March 18, 2022	Approved
Node JS (Install) 14.19.0	4251	Tuesday, February 1, 2022	Approved
Node JS (Install) 14.18.3	5470	Tuesday, January 11, 2022	Approved
Node JS (Install) 14.18.2	4421	Tuesday, November 30, 2021	Approved
Node JS (Install) 14.18.1	7695	Tuesday, October 12, 2021	Approved
Node JS (Install) 14.18.0	3772	Tuesday, September 28, 2021	Approved
Node JS (Install) 14.17.5	9306	Wednesday, August 11, 2021	Approved
Node JS (Install) 14.17.4	419	Thursday, July 29, 2021	Approved
Node JS (Install) 14.17.3	2876	Monday, July 5, 2021	Approved
Node JS (Install) 14.17.2	234	Thursday, July 1, 2021	Approved
Node JS (Install) 14.17.1	945	Tuesday, June 15, 2021	Approved
Node JS (Install) 14.17.0	18616	Wednesday, May 12, 2021	Approved
Node JS (Install) 14.16.1	6872	Wednesday, April 7, 2021	Approved
Node JS (Install) 14.15.5	3002	Tuesday, February 9, 2021	Approved
Node JS (Install) 14.15.4	18558	Tuesday, January 5, 2021	Approved
Node JS (Install) 14.15.3	1305	Friday, December 18, 2020	Approved
Node JS (Install) 14.15.2	373	Wednesday, December 16, 2020	Approved
Node JS (Install) 14.15.1	2089	Monday, November 16, 2020	Approved
Node JS (Install) 14.15.0	11262	Tuesday, October 27, 2020	Approved
Node JS (Install) 14.14.0	10634	Friday, October 16, 2020	Approved
Node JS (Install) 14.13.1	27336	Thursday, October 8, 2020	Approved
Node JS (Install) 14.13.0	21606	Wednesday, September 30, 2020	Approved
Node JS (Install) 14.12.0	20220	Wednesday, September 23, 2020	Approved
Node JS (Install) 14.11.0	19691	Wednesday, September 16, 2020	Approved
Node JS (Install) 14.10.1	14907	Thursday, September 10, 2020	Approved
Node JS (Install) 14.10.0	7962	Tuesday, September 8, 2020	Approved
Node JS (Install) 14.8.0	60060	Tuesday, August 11, 2020	Approved
Node JS (Install) 14.7.0	27663	Friday, July 31, 2020	Approved
Node JS (Install) 14.6.0	23899	Wednesday, July 22, 2020	Approved
Node JS (Install) 14.5.0	44611	Wednesday, July 1, 2020	Approved
Node JS (Install) 14.4.0	55444	Wednesday, June 3, 2020	Approved
Node JS (Install) 14.3.0	29870	Wednesday, May 20, 2020	Approved
Node JS (Install) 14.2.0	33683	Wednesday, May 6, 2020	Approved
Node JS (Install) 14.1.0	12246	Thursday, April 30, 2020	Approved
Node JS (Install) 14.0.0	24763	Wednesday, April 22, 2020	Approved
Node JS (Install) 13.14.0	44870	Tuesday, June 2, 2020	Approved
Node JS (Install) 13.13.0	19138	Wednesday, April 15, 2020	Approved
Node JS (Install) 13.12.0	42636	Friday, March 27, 2020	Approved
Node JS (Install) 13.11.0	28997	Thursday, March 12, 2020	Approved
Node JS (Install) 13.10.1	21222	Thursday, March 5, 2020	Approved
Node JS (Install) 13.9.0	31899	Wednesday, February 19, 2020	Approved
Node JS (Install) 13.7.0	47065	Wednesday, January 22, 2020	Approved
Node JS (Install) 13.6.0	18637	Wednesday, January 8, 2020	Approved
Node JS (Install) 13.5.0	38097	Friday, December 20, 2019	Approved
Node JS (Install) 13.3.0	25884	Thursday, December 5, 2019	Approved
Node JS (Install) 13.2.0	25523	Friday, November 22, 2019	Approved
Node JS (Install) 13.1.0	21477	Monday, November 11, 2019	Approved
Node JS (Install) 13.0.1	36355	Wednesday, October 23, 2019	Approved
Node JS (Install) 13.0.0	5342	Tuesday, October 22, 2019	Approved
Node JS (Install) 12.22.12	1621	Tuesday, April 5, 2022	Approved
Node JS (Install) 12.22.11	314	Friday, March 18, 2022	Approved
Node JS (Install) 12.22.10	253	Wednesday, February 2, 2022	Approved
Node JS (Install) 12.22.9	706	Tuesday, January 11, 2022	Approved
Node JS (Install) 12.22.8	177	Friday, December 17, 2021	Approved
Node JS (Install) 12.22.7	1157	Tuesday, October 12, 2021	Approved
Node JS (Install) 12.22.6	1994	Tuesday, August 31, 2021	Approved
Node JS (Install) 12.22.5	405	Wednesday, August 11, 2021	Approved
Node JS (Install) 12.22.4	142	Thursday, July 29, 2021	Approved
Node JS (Install) 12.22.3	548	Monday, July 5, 2021	Approved
Node JS (Install) 12.22.2	139	Thursday, July 1, 2021	Approved
Node JS (Install) 12.22.1	2868	Wednesday, April 7, 2021	Approved
Node JS (Install) 12.22.0	8257	Tuesday, March 30, 2021	Approved
Node JS (Install) 12.21.0	5206	Tuesday, February 23, 2021	Approved
Node JS (Install) 12.20.2	470	Thursday, February 11, 2021	Approved
Node JS (Install) 12.20.1	5197	Tuesday, January 5, 2021	Approved
Node JS (Install) 12.20.0	1608	Tuesday, November 24, 2020	Approved
Node JS (Install) 12.19.1	463	Monday, November 16, 2020	Approved
Node JS (Install) 12.19.0	3821	Wednesday, October 7, 2020	Approved
Node JS (Install) 12.18.4	1601	Wednesday, September 16, 2020	Approved
Node JS (Install) 12.18.3	14820	Wednesday, July 22, 2020	Approved
Node JS (Install) 12.18.2	2226	Tuesday, June 30, 2020	Approved
Node JS (Install) 12.18.1	1044	Wednesday, June 17, 2020	Approved
Node JS (Install) 12.18.0	2659	Wednesday, June 3, 2020	Approved
Node JS (Install) 12.17.0	2299	Tuesday, May 26, 2020	Approved
Node JS (Install) 12.16.3	5544	Tuesday, April 28, 2020	Approved
Node JS (Install) 12.16.2	2330	Thursday, April 9, 2020	Approved
Node JS (Install) 12.16.1	9593	Wednesday, February 19, 2020	Approved
Node JS (Install) 12.16.0	2787	Wednesday, February 12, 2020	Approved
Node JS (Install) 12.15.0	4672	Thursday, February 6, 2020	Approved
Node JS (Install) 12.14.1	22221	Tuesday, January 7, 2020	Approved
Node JS (Install) 12.14.0	3136	Wednesday, December 18, 2019	Approved
Node JS (Install) 12.13.1	7298	Tuesday, November 19, 2019	Approved
Node JS (Install) 12.13.0	22346	Monday, October 21, 2019	Approved
Node JS (Install) 12.12.0	19621	Saturday, October 12, 2019	Approved
Node JS (Install) 12.11.1	21911	Tuesday, October 1, 2019	Approved
Node JS (Install) 12.11.0	14884	Thursday, September 26, 2019	Approved
Node JS (Install) 12.10.0	45627	Thursday, September 5, 2019	Approved
Node JS (Install) 12.9.1	33502	Tuesday, August 27, 2019	Approved
Node JS (Install) 12.9.0	14667	Wednesday, August 21, 2019	Approved
Node JS (Install) 12.8.1	13606	Thursday, August 15, 2019	Approved
Node JS (Install) 12.8.0	23942	Wednesday, August 7, 2019	Approved
Node JS (Install) 12.7.0	24580	Wednesday, July 24, 2019	Approved
Node JS (Install) 12.6.0	34229	Wednesday, July 3, 2019	Approved
Node JS (Install) 12.5.0	11899	Thursday, June 27, 2019	Approved
Node JS (Install) 12.4.0	40404	Tuesday, June 4, 2019	Approved
Node JS (Install) 12.3.1	22569	Wednesday, May 22, 2019	Approved
Node JS (Install) 12.3.0	1728	Wednesday, May 22, 2019	Approved
Node JS (Install) 12.2.0	24243	Wednesday, May 8, 2019	Approved
Node JS (Install) 12.1.0	26097	Monday, April 29, 2019	Approved
Node JS (Install) 12.0.0	13022	Tuesday, April 23, 2019	Approved
Node JS (Install) 11.15.0	7291	Tuesday, April 30, 2019	Approved
Node JS (Install) 11.14.0	21478	Thursday, April 11, 2019	Approved
Node JS (Install) 11.13.0	25933	Friday, March 29, 2019	Approved
Node JS (Install) 11.12.0	22328	Saturday, March 16, 2019	Approved
Node JS (Install) 11.11.0	17165	Thursday, March 7, 2019	Approved
Node JS (Install) 11.10.1	12952	Thursday, February 28, 2019	Approved
Node JS (Install) 11.10.0	21639	Friday, February 15, 2019	Approved
Node JS (Install) 11.9.0	27011	Thursday, January 31, 2019	Approved
Node JS (Install) 11.8.0	10496	Friday, January 25, 2019	Approved
Node JS (Install) 11.7.0	11430	Friday, January 18, 2019	Approved
Node JS (Install) 11.6.0	32696	Wednesday, December 26, 2018	Approved
Node JS (Install) 11.5.0	9865	Wednesday, December 19, 2018	Approved
Node JS (Install) 11.4.0	16335	Friday, December 7, 2018	Approved
Node JS (Install) 11.3.0	14154	Wednesday, November 28, 2018	Approved
Node JS (Install) 11.2.0	4102	Monday, November 26, 2018	Approved
Node JS (Install) 10.24.1	2513	Wednesday, April 7, 2021	Approved
Node JS (Install) 10.24.0	559	Tuesday, February 23, 2021	Approved
Node JS (Install) 10.23.3	239	Wednesday, February 10, 2021	Approved
Node JS (Install) 10.23.2	182	Tuesday, January 26, 2021	Approved
Node JS (Install) 10.23.1	4405	Tuesday, January 5, 2021	Approved
Node JS (Install) 10.23.0	4268	Tuesday, October 27, 2020	Approved
Node JS (Install) 10.22.1	837	Wednesday, September 16, 2020	Approved
Node JS (Install) 10.22.0	3816	Tuesday, July 21, 2020	Approved
Node JS (Install) 10.21.0	1573	Wednesday, June 3, 2020	Approved
Node JS (Install) 10.20.1	4568	Sunday, April 12, 2020	Approved
Node JS (Install) 10.20.0	650	Wednesday, April 8, 2020	Approved
Node JS (Install) 10.19.0	953	Thursday, February 6, 2020	Approved
Node JS (Install) 10.18.1	1791	Friday, January 10, 2020	Approved
Node JS (Install) 10.18.0	1001	Wednesday, December 18, 2019	Approved
Node JS (Install) 10.17.0	4348	Tuesday, October 22, 2019	Approved
Node JS (Install) 10.16.3	40250	Friday, August 16, 2019	Approved
Node JS (Install) 10.16.2	1795	Wednesday, August 7, 2019	Approved
Node JS (Install) 10.16.1	5060	Thursday, August 1, 2019	Approved
Node JS (Install) 10.16.0	7276	Wednesday, May 29, 2019	Approved
Node JS (Install) 10.15.3	7066	Tuesday, March 5, 2019	Approved
Node JS (Install) 10.15.2	888	Thursday, February 28, 2019	Approved
Node JS (Install) 10.15.1	11892	Wednesday, January 30, 2019	Approved
Node JS (Install) 10.15.0	4526	Wednesday, December 26, 2018	Approved
Node JS (Install) 10.14.2	2807	Wednesday, December 12, 2018	Approved
Node JS (Install) 10.14.1	3272	Thursday, November 29, 2018	Approved
Node JS (Install) 10.14.0	1003	Wednesday, November 28, 2018	Approved
Node JS (Install) 10.13.0	38850	Tuesday, October 30, 2018	Approved
Node JS (Install) 10.12.0	15163	Tuesday, October 16, 2018	Approved
Node JS (Install) 10.11.0	46022	Thursday, September 20, 2018	Approved
Node JS (Install) 10.10.0	25692	Friday, September 7, 2018	Approved
Node JS (Install) 10.9.0	37180	Thursday, August 16, 2018	Approved
Node JS (Install) 10.8.0	31568	Thursday, August 2, 2018	Approved
Node JS (Install) 10.7.0	27720	Thursday, July 19, 2018	Approved
Node JS (Install) 10.6.0	24739	Wednesday, July 4, 2018	Approved
Node JS (Install) 10.5.0	26523	Thursday, June 21, 2018	Approved
Node JS (Install) 10.4.1	14117	Wednesday, June 13, 2018	Approved
Node JS (Install) 10.4.0	11244	Wednesday, June 6, 2018	Approved
Node JS (Install) 10.3.0	16204	Tuesday, May 29, 2018	Approved
Node JS (Install) 10.2.1	8415	Friday, May 25, 2018	Approved
Node JS (Install) 10.2.0	3676	Thursday, May 24, 2018	Approved
Node JS (Install) 10.1.0	30889	Wednesday, May 9, 2018	Approved
Node JS (Install) 10.0.0	26682	Wednesday, April 25, 2018	Approved
Node JS (Install) 9.11.2	834	Saturday, May 4, 2019	Approved
Node JS (Install) 9.11.1	33895	Thursday, April 5, 2018	Approved
Node JS (Install) 9.10.1	10850	Friday, March 30, 2018	Approved
Node JS (Install) 9.10.0	4156	Wednesday, March 28, 2018	Approved
Node JS (Install) 9.9.0	15145	Wednesday, March 21, 2018	Approved
Node JS (Install) 9.8.0	27510	Thursday, March 8, 2018	Approved
Node JS (Install) 9.7.1	11069	Friday, March 2, 2018	Approved
Node JS (Install) 9.7.0	2433	Thursday, March 1, 2018	Approved
Node JS (Install) 9.6.1	9248	Friday, February 23, 2018	Approved
Node JS (Install) 9.6.0	4060	Thursday, February 22, 2018	Approved
Node JS (Install) 9.5.0	30537	Thursday, February 1, 2018	Approved
Node JS (Install) 9.4.0	34602	Wednesday, January 10, 2018	Approved
Node JS (Install) 9.3.0	34405	Wednesday, December 13, 2017	Approved
Node JS (Install) 9.2.1	3235	Friday, December 8, 2017	Approved
Node JS (Install) 9.2.0	47565	Wednesday, November 15, 2017	Approved
Node JS (Install) 9.1.0	11099	Tuesday, November 7, 2017	Approved
Node JS (Install) 9.0.0	15177	Tuesday, October 31, 2017	Approved
Node JS (Install) 8.17.0	8338	Wednesday, December 18, 2019	Approved
Node JS (Install) 8.16.2	695	Thursday, October 10, 2019	Approved
Node JS (Install) 8.16.1	531	Friday, August 16, 2019	Approved
Node JS (Install) 8.16.0	2168	Wednesday, April 17, 2019	Approved
Node JS (Install) 8.15.1	1248	Thursday, February 28, 2019	Approved
Node JS (Install) 8.15.0	1630	Wednesday, December 26, 2018	Approved
Node JS (Install) 8.14.1	334	Tuesday, December 18, 2018	Approved
Node JS (Install) 8.14.0	724	Wednesday, November 28, 2018	Approved
Node JS (Install) 8.13.0	456	Wednesday, November 21, 2018	Approved
Node JS (Install) 8.12.0	8509	Tuesday, September 11, 2018	Approved
Node JS (Install) 8.11.4	4524	Thursday, August 16, 2018	Approved
Node JS (Install) 8.11.3	7480	Wednesday, June 13, 2018	Approved
Node JS (Install) 8.11.2	2076	Wednesday, May 16, 2018	Approved
Node JS (Install) 8.11.1	3296	Friday, March 30, 2018	Approved
Node JS (Install) 8.11.0	1366	Wednesday, March 28, 2018	Approved
Node JS (Install) 8.10.0	5168	Wednesday, March 7, 2018	Approved
Node JS (Install) 8.9.4	64173	Wednesday, January 3, 2018	Approved
Node JS (Install) 8.9.3	13025	Friday, December 8, 2017	Approved
Node JS (Install) 8.9.2	732	Wednesday, December 6, 2017	Approved
Node JS (Install) 8.9.1	25356	Wednesday, November 8, 2017	Approved
Node JS (Install) 8.9.0.20171107	543	Tuesday, November 7, 2017	Approved
Node JS (Install) 8.8.1	9838	Thursday, October 26, 2017	Approved
Node JS (Install) 8.8.0	2453	Wednesday, October 25, 2017	Approved
Node JS (Install) 8.7.0	19474	Thursday, October 12, 2017	Approved
Node JS (Install) 8.6.0.20170927	21516	Wednesday, September 27, 2017	Approved
Node JS (Install) 8.6.0	1123	Wednesday, September 27, 2017	Approved
Node JS (Install) 8.5.0	24790	Tuesday, September 12, 2017	Approved
Node JS (Install) 8.4.0	45382	Wednesday, August 16, 2017	Approved
Node JS (Install) 8.3.0	10245	Thursday, August 10, 2017	Approved
Node JS (Install) 8.2.1	31907	Friday, July 21, 2017	Approved
Node JS (Install) 8.2.0	2767	Thursday, July 20, 2017	Approved
Node JS (Install) 8.1.4	15315	Tuesday, July 11, 2017	Approved
Node JS (Install) 8.1.3	22734	Thursday, June 29, 2017	Approved
Node JS (Install) 8.1.2	44709	Thursday, June 15, 2017	Approved
Node JS (Install) 8.1.1	15548	Wednesday, June 14, 2017	Approved
Node JS (Install) 8.1.0	22427	Thursday, June 8, 2017	Approved
Node JS (Install) 8.0.0	65452	Wednesday, May 31, 2017	Approved
Node JS (Install) 7.10.1	382	Saturday, May 4, 2019	Approved
Node JS (Install) 7.10.0	83588	Wednesday, May 3, 2017	Approved
Node JS (Install) 7.9.0	34020	Wednesday, April 12, 2017	Approved
Node JS (Install) 7.8.0	23670	Wednesday, March 29, 2017	Approved
Node JS (Install) 7.7.4	13639	Wednesday, March 22, 2017	Approved
Node JS (Install) 7.7.3	13214	Wednesday, March 15, 2017	Approved
Node JS (Install) 7.7.2	11416	Thursday, March 9, 2017	Approved
Node JS (Install) 7.7.1	14732	Thursday, March 2, 2017	Approved
Node JS (Install) 7.7.0	3424	Wednesday, March 1, 2017	Approved
Node JS (Install) 7.6.0	11839	Wednesday, February 22, 2017	Approved
Node JS (Install) 7.5.0	33542	Wednesday, February 1, 2017	Approved
Node JS (Install) 7.4.0	12224	Tuesday, January 24, 2017	Approved
Node JS (Install) 7.3.0	36906	Tuesday, December 20, 2016	Approved
Node JS (Install) 7.2.1	25690	Wednesday, December 7, 2016	Approved
Node JS (Install) 7.2.0	39231	Wednesday, November 23, 2016	Approved
Node JS (Install) 7.1.0	37648	Tuesday, November 8, 2016	Approved
Node JS (Install) 7.0.0	19215	Tuesday, October 25, 2016	Approved
Node JS (Install) 6.17.1	2475	Thursday, April 4, 2019	Approved
Node JS (Install) 6.17.0	271	Thursday, February 28, 2019	Approved
Node JS (Install) 6.16.0	532	Wednesday, December 26, 2018	Approved
Node JS (Install) 6.15.1	325	Monday, December 3, 2018	Approved
Node JS (Install) 6.15.0	297	Wednesday, November 28, 2018	Approved
Node JS (Install) 6.14.4	687	Thursday, August 16, 2018	Approved
Node JS (Install) 6.14.3	606	Wednesday, June 13, 2018	Approved
Node JS (Install) 6.14.2	485	Monday, April 30, 2018	Approved
Node JS (Install) 6.14.1	547	Friday, March 30, 2018	Approved
Node JS (Install) 6.14.0	465	Wednesday, March 28, 2018	Approved
Node JS (Install) 6.13.1	666	Wednesday, March 7, 2018	Approved
Node JS (Install) 6.13.0	571	Wednesday, February 14, 2018	Approved
Node JS (Install) 6.12.3	9212	Wednesday, January 3, 2018	Approved
Node JS (Install) 6.12.2	545	Friday, December 8, 2017	Approved
Node JS (Install) 6.12.1	447	Tuesday, December 5, 2017	Approved
Node JS (Install) 6.12.0	910	Tuesday, November 7, 2017	Approved
Node JS (Install) 6.11.5	11220	Thursday, November 2, 2017	Approved
Node JS (Install) 6.11.0	2106	Wednesday, June 21, 2017	Approved
Node JS (Install) 6.9.5	21915	Friday, February 3, 2017	Approved
Node JS (Install) 6.9.4	4738	Friday, February 3, 2017	Approved
Node JS (Install) 6.9.3	612	Friday, February 3, 2017	Approved
Node JS (Install) 6.9.1	27216	Wednesday, October 19, 2016	Approved
Node JS (Install) 6.8.1	8846	Saturday, October 15, 2016	Approved
Node JS (Install) 6.8.0	5267	Wednesday, October 12, 2016	Approved
Node JS (Install) 6.7.0	66782	Wednesday, September 28, 2016	Approved
Node JS (Install) 6.6.0	16594	Thursday, September 15, 2016	Approved
Node JS (Install) 6.5.0	14555	Monday, August 29, 2016	Approved
Node JS (Install) 6.4.0	10990	Tuesday, August 16, 2016	Approved
Node JS (Install) 6.3.1	14971	Friday, July 22, 2016	Approved
Node JS (Install) 6.3.0	1996	Sunday, July 17, 2016	Approved
Node JS (Install) 6.2.2	3191	Friday, June 17, 2016	Approved
Node JS (Install) 6.2.1	791	Thursday, June 2, 2016	Approved
Node JS (Install) 6.2.0	736	Tuesday, May 17, 2016	Approved
Node JS (Install) 6.1.0	2344	Sunday, May 8, 2016	Approved
Node JS (Install) 5.12.0	274	Saturday, May 4, 2019	Approved
Node JS (Install) 5.10.1	65241	Wednesday, April 6, 2016	Approved
Node JS (Install) 5.10.0	3355	Friday, April 1, 2016	Approved
Node JS (Install) 5.9.1	4105	Wednesday, March 23, 2016	Approved
Node JS (Install) 5.9.0	3581	Wednesday, March 16, 2016	Approved
Node JS (Install) 5.8.0	3613	Thursday, March 10, 2016	Approved
Node JS (Install) 5.7.1	3496	Thursday, March 3, 2016	Approved
Node JS (Install) 5.7.0	6235	Tuesday, February 23, 2016	Approved
Node JS (Install) 5.6.0	5669	Tuesday, February 9, 2016	Approved
Node JS (Install) 5.5.0	6782	Thursday, January 21, 2016	Approved
Node JS (Install) 5.4.1	3665	Wednesday, January 13, 2016	Approved
Node JS (Install) 5.4.0	2879	Wednesday, January 6, 2016	Approved
Node JS (Install) 5.3.0	6003	Wednesday, December 16, 2015	Approved
Node JS (Install) 5.2.0	59161	Wednesday, December 9, 2015	Approved
Node JS (Install) 5.1.1	90417	Friday, December 4, 2015	Approved
Node JS (Install) 5.1.0	174778	Tuesday, November 17, 2015	Approved
Node JS (Install) 5.0.0	4811	Friday, November 6, 2015	Approved
Node JS (Install) 4.9.1	614	Friday, March 30, 2018	Approved
Node JS (Install) 4.9.0	399	Wednesday, March 28, 2018	Approved
Node JS (Install) 4.8.7	517	Friday, December 8, 2017	Approved
Node JS (Install) 4.8.6	544	Tuesday, November 7, 2017	Approved
Node JS (Install) 4.8.5	657	Thursday, November 2, 2017	Approved
Node JS (Install) 4.6.1	1070	Tuesday, October 18, 2016	Approved
Node JS (Install) 4.6.0	1077	Tuesday, October 18, 2016	Approved
Node JS (Install) 4.5.0	969	Tuesday, October 18, 2016	Approved
Node JS (Install) 4.4.7	2664	Wednesday, July 6, 2016	Approved
Node JS (Install) 4.4.6	569	Wednesday, July 6, 2016	Approved
Node JS (Install) 4.4.5	880	Tuesday, May 31, 2016	Approved
Node JS (Install) 4.4.4	680	Monday, May 9, 2016	Approved
Node JS (Install) 4.4.3	1017	Thursday, April 14, 2016	Approved
Node JS (Install) 4.4.2	669	Wednesday, April 27, 2016	Approved
Node JS (Install) 4.4.0	1577	Thursday, March 10, 2016	Approved
Node JS (Install) 4.3.2	862	Thursday, March 3, 2016	Approved
Node JS (Install) 4.3.1	2857	Wednesday, February 17, 2016	Approved
Node JS (Install) 4.3.0	629	Tuesday, February 9, 2016	Approved
Node JS (Install) 4.2.6	873	Friday, January 22, 2016	Approved
Node JS (Install) 4.2.5	599	Thursday, January 21, 2016	Approved
Node JS (Install) 4.2.4	966	Wednesday, January 13, 2016	Approved
Node JS (Install) 4.2.3	531	Wednesday, January 13, 2016	Approved
Node JS (Install) 4.2.2	3821	Friday, November 6, 2015	Approved
Node JS (Install) 4.2.1	869	Friday, November 6, 2015	Approved
Node JS (Install) 4.2.0	685	Friday, November 6, 2015	Approved
Node JS (Install) 4.1.2	12176	Monday, October 5, 2015	Approved
Node JS (Install) 4.1.1	5050	Wednesday, September 23, 2015	Approved
Node JS (Install) 4.1.0	2944	Thursday, September 17, 2015	Approved
Node JS (Install) 4.0.0	3581	Thursday, September 10, 2015	Approved
Node JS (Install) 0.12.7	20770	Sunday, July 12, 2015	Approved
Node JS (Install) 0.12.6	3109	Saturday, July 4, 2015	Approved
Node JS (Install) 0.12.5	3936	Wednesday, June 24, 2015	Approved
Node JS (Install) 0.12.4	9135	Monday, May 25, 2015	Approved
Node JS (Install) 0.12.3	4284	Friday, May 15, 2015	Approved
Node JS (Install) 0.12.2	15153	Wednesday, April 1, 2015	Approved
Node JS (Install) 0.12.1	3477	Tuesday, March 24, 2015	Approved
Node JS (Install) 0.12.0	14908	Saturday, February 7, 2015	Approved
Node JS (Install) 0.10.36	3562	Tuesday, January 27, 2015	Approved
Node JS (Install) 0.10.35	5201	Friday, December 26, 2014	Approved
Node JS (Install) 0.10.34	1503	Thursday, December 18, 2014	Approved
Node JS (Install) 0.10.33	5627	Wednesday, October 29, 2014	Approved
Node JS (Install) 0.10.32	4386	Wednesday, September 17, 2014	Approved
Node JS (Install) 0.10.31	2928	Wednesday, August 20, 2014	Approved
Node JS (Install) 0.10.30	2580	Friday, August 1, 2014	Approved
Node JS (Install) 0.10.29	4296	Tuesday, June 17, 2014	Approved
Node JS (Install) 0.10.28	3816	Saturday, May 3, 2014	Approved
Node JS (Install) 0.10.27	654	Friday, May 2, 2014	Approved
Node JS (Install) 0.10.26	5257	Wednesday, February 19, 2014	Approved
Node JS (Install) 0.10.25	2013	Friday, January 24, 2014	Approved
Node JS (Install) 0.10.24	2185	Friday, December 20, 2013	Approved
Node JS (Install) 0.10.23	1016	Thursday, December 12, 2013	Approved
Node JS (Install) 0.10.22	1814	Wednesday, November 13, 2013	Approved
Node JS (Install) 0.10.21	1646	Saturday, October 19, 2013	Approved
Node JS (Install) 0.10.20	1377	Tuesday, October 1, 2013	Approved
Node JS (Install) 0.10.19	954	Wednesday, September 25, 2013	Approved
Node JS (Install) 0.10.18	1378	Thursday, September 5, 2013	Approved
Node JS (Install) 0.10.17	1155	Thursday, August 22, 2013	Approved
Node JS (Install) 0.10.16	879	Saturday, August 17, 2013	Approved
Node JS (Install) 0.10.15	1383	Friday, July 26, 2013	Approved
Node JS (Install) 0.10.13	1138	Wednesday, July 10, 2013	Approved
Node JS (Install) 0.10.12	1371	Wednesday, June 19, 2013	Approved
Node JS (Install) 0.10.11	783	Friday, June 14, 2013	Approved
Node JS (Install) 0.10.10	901	Wednesday, June 5, 2013	Approved
Node JS (Install) 0.10.9	905	Friday, May 31, 2013	Approved
Node JS (Install) 0.10.8	898	Saturday, May 25, 2013	Approved
Node JS (Install) 0.10.7	773	Monday, May 20, 2013	Approved
Node JS (Install) 0.10.6	764	Wednesday, May 15, 2013	Approved
Node JS (Install) 0.10.5	1829	Wednesday, April 24, 2013	Approved
Node JS (Install) 0.10.4	887	Friday, April 12, 2013	Approved
Node JS (Install) 0.10.3	969	Thursday, April 4, 2013	Approved
Node JS (Install) 0.10.2	792	Friday, March 29, 2013	Approved
Node JS (Install) 0.10.1	833	Friday, March 22, 2013	Approved
Node JS (Install) 0.10.0	972	Tuesday, March 12, 2013	Approved
Node JS (Install) 0.8.22	4985	Thursday, March 7, 2013	Approved
Node JS (Install) 0.8.21.20130226	890	Tuesday, February 26, 2013	Approved
Node JS (Install) 0.8.21	690	Tuesday, February 26, 2013	Approved
Node JS (Install) 0.8.20.20130224	741	Sunday, February 24, 2013	Approved
Node JS (Install) 0.8.20	988	Saturday, February 16, 2013	Approved
Node JS (Install) 0.8.19	1076	Thursday, February 7, 2013	Approved
Node JS (Install) 0.8.18	1371	Saturday, January 19, 2013	Approved
Node JS (Install) 0.8.17	1039	Thursday, January 10, 2013	Approved
Node JS (Install) 0.8.16	1194	Friday, December 14, 2012	Approved
Node JS (Install) 0.8.15	8972	Tuesday, November 27, 2012	Approved
Node JS (Install) 0.8.14	1328	Friday, October 26, 2012	Approved
Node JS (Install) 0.8.12	903	Sunday, October 14, 2012	Approved
Node JS (Install) 0.8.11	917	Friday, September 28, 2012	Approved
Node JS (Install) 0.8.10	876	Wednesday, September 26, 2012	Approved
Node JS (Install) 0.8.9.20120913	972	Thursday, September 13, 2012	Approved
Node JS (Install) 0.8.9	686	Wednesday, September 12, 2012	Approved
Node JS (Install) 0.8.8	736	Sunday, August 26, 2012	Approved
Node JS (Install) 0.8.7	738	Thursday, August 16, 2012	Approved
Node JS (Install) 0.8.6	769	Wednesday, August 8, 2012	Approved
Node JS (Install) 0.8.5	719	Monday, August 6, 2012	Approved
Node JS (Install) 0.8.4	788	Friday, July 27, 2012	Approved
Node JS (Install) 0.8.3	721	Friday, July 20, 2012	Approved
Node JS (Install) 0.8.2	676	Tuesday, July 10, 2012	Approved
Node JS (Install) 0.8.1	938	Friday, June 29, 2012	Approved
Node JS (Install) 0.6.19	792	Friday, June 8, 2012	Approved
Node JS (Install) 0.6.18	786	Monday, May 21, 2012	Approved
Node JS (Install) 0.6.17	807	Friday, May 11, 2012	Approved
Node JS (Install) 0.6.16	640	Friday, May 11, 2012	Approved
Node JS (Install) 0.6.15	748	Wednesday, April 11, 2012	Approved
Node JS (Install) 0.6.14	658	Sunday, April 1, 2012	Approved
Node JS (Install) 0.6.13	666	Sunday, April 1, 2012	Approved
Node JS (Install) 0.6.12	707	Saturday, March 10, 2012	Approved
Node JS (Install) 0.6.11	747	Saturday, February 25, 2012	Approved
Node JS Install 0.6.10	737	Monday, February 6, 2012	Approved
Node JS Install 0.6.9	720	Monday, February 6, 2012	Approved
Node JS Install 0.6.8	756	Sunday, January 22, 2012	Approved
Node JS Install 0.6.7	668	Sunday, January 15, 2012	Approved
Node JS Install 0.6.6	719	Sunday, December 18, 2011	Approved

Dependencies

This package has no dependencies.

Discussion for the Node JS (Install) Package

Ground Rules:

This discussion is only about Node JS (Install) and the Node JS (Install) 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 (Install), 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.

Resources

Events

Courses

7,357,307

556

25 Apr 2024

Node JS (Install)

Node JS (Install) 20.12.2

All Checks are Passing

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Notes

Ground Rules: