附加工具安装了许多项目及其依赖项，如在脚本中提到的那样。这些项将用于需要使用这些工具编译任何节点模块的情况。
此脚本将安装Python和Visual Studio构建工具，这是编译Node.js本地模块所必需的。请注意，Chocolatey和所需的Windows更新也将安装。
这将需要大约3 GB的可用磁盘空间，以及安装Windows更新所需的任何空间。这将需要一段时间来运行。
node-v16.13.0-x64.msi示例

- https://chocolatey.org/packages/chocolatey
- https://chocolatey.org/packages/python
- https://chocolatey.org/packages/visualstudio2019-workload-vctools

特别是visualstudio 2019-workload-vctools需要下载1.6 gig的构建工具，这可能需要一段时间。
如果您想知道事情是否正在进行中，请尝试启动Visual Studio插件。如果安装程序仍在运行，您可能会收到一条消息：“当此示例正在运行时，无法启动安装程序的另一个示例”。
如果你已经退出，重新启动，并重新启动脚本，你仍然想知道是否所有的工具都安装了，你可以做以下事情：

• 键入choco list查看是否安装了软件包visualstudio-installer、visualstudio2019-workload-vctools和visualstudio2019buildtools
• 打开Visual Studio安装包，您可以查看安装程序是否已完成构建工具的安装。可能需要恢复。
  

注意：已更新，从choco list命令中删除了不推荐使用的-lo

今天同样的问题。我刚刚让Windows Powershell停止并冻结了大约5分钟，同时安装Node.JS for VS Code（而不是Visual Studio）。控制台的最后输出为：
$创建了一个UnelevatedInstallerTelemetryDecorator
长话短说：我不得不退出终端（不喜欢这个动作）并重新启动计算机，因为安装程序仍在运行。然后我点击安装文件运行Node.js安装向导（node-v15.14.0-x64.msi）。还有第二个选项可以修复安装尝试：“修复”。单击该按钮，安装向导将完成修复并完全退出。程序会注意到某些元素尚未完成。然后你可以在VS Code中的终端上运行一个JavaScript文件。
我不需要修复VS代码。
从VS代码终端运行的示例（终端条目以粗体显示）
PS“驱动器位置”\JavaScript>节点canDrinkNoIfs.js
要在VSC中运行脚本，我需要打开文件夹（File -> open folder.），然后创建一个json文件来运行和调试代码。这个json文件保存在.vscode子文件夹中。

{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
    {
        "type": "pwa-node",
        "request": "launch",
        "name": "Launch Program",
        "skipFiles": [
            "<node_internals>/**"
        ],
        "program": "${workspaceFolder}\\canDrinkNoifs.js"
    }]}

发生在我身上
首先尝试使用space或tab。在我的第一站PowerShell中，

Download of vs_BuildTools.exe (1.4 MB) completed.
Hashes match.
Installing visualstudio2017buildtools...

在工作
伙计们，如果你使用空格或制表符，然后工作：这是因为你在PowerShell中使用点击鼠标，不要这样做，有时会暂停程序：）[如果正在工作，是一个正常的错误，它不会对完成下载造成任何危险]
但我有很多白色文字。最后一站是

[1968:0007][2021-08-24T19:47:57] Created a UnelevatedInstallerTelemetryDecorator

here the error you have.❌

用于更正此错误.做这个！

• 转到边缘（或您选择下载的浏览器）
• 转到下载选项卡，其中有node-v14.17.5-x64.msi（边缘为CTRL+J）
• 打开文件
• 点击修复，就是这样

我会把一些照片的最终结果，如果你需要它：
final result SUCCESS✅

编辑

过了一会儿，我有这个，在同一个powershell我有第一站。

Chocolatey timed out waiting for the command to finish. The timeout
 specified (or the default value) was '2700' seconds. Perhaps try a
 higher `--execution-timeout`? See `choco -h` for details.
  visualstudio2017-workload-vctools may be able to be automatically uninstalled.
The upgrade of visualstudio2017-workload-vctools was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\visualstudio2017-workload-vctools\tools\ChocolateyInstall.ps1'.
 See log for details.

Chocolatey upgraded 15/17 packages. 2 packages failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Upgraded:
 - chocolatey-dotnetfx.extension v1.0.1
 - kb3033929 v1.0.5
 - visualstudio2017buildtools v15.9.38.0
 - chocolatey-windowsupdate.extension v1.0.4
 - vcredist140 v14.29.30133
 - kb2999226 v1.0.20181019
 - visualstudio-installer v2.0.1
 - kb2919355 v1.0.20160915
 - chocolatey-core.extension v1.3.5.1
 - kb2919442 v1.0.20160915
 - chocolatey-visualstudio.extension v1.9.0
 - vcredist2015 v14.0.24215.20170201
 - dotnetfx v4.8.0.20190930
 - kb3035131 v1.0.3
 - python v3.9.6

Failures
 - python3 (exited 1603) - Error while running 'C:\ProgramData\chocolatey\lib\python3\tools\chocolateyInstall.ps1'.
 See log for details.
 - visualstudio2017-workload-vctools (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\visualstudio2017-workload-vctools\tools\ChocolateyInstall.ps1'.
 See log for details.

最后是TYPE ENTER FOR EXIT - message on powershell

如果您看到最后一条消息。

See "choco -h" for details.所以，我用PowerShell写的。

我有这个结果，有一个绿色消息，最后，有版本

This is a listing of all of the different things you can pass to choco.

Commands

 * list - lists remote or local packages
 * find - searches remote or local packages (alias for search)
 * search - searches remote or local packages (alias for list)
 * info - retrieves package information. Shorthand for choco search pkgname --exact --verbose
 * install - installs packages from various sources
 * pin - suppress upgrades for a package
 * outdated - retrieves packages that are outdated. Similar to upgrade all --noop
 * upgrade - upgrades packages from various sources
 * uninstall - uninstalls a package
 * pack - packages up a nuspec to a compiled nupkg
 * push - pushes a compiled nupkg
 * new - generates files necessary for a chocolatey package from a template
 * sources - view and configure default sources (alias for source)
 * source - view and configure default sources
 * config - Retrieve and configure config file settings
 * feature - view and configure choco features
 * features - view and configure choco features (alias for feature)
 * setapikey - retrieves, saves or deletes an apikey for a particular source (alias for apikey)
 * apikey - retrieves, saves or deletes an apikey for a particular source
 * unpackself - have chocolatey set itself up
 * version - [DEPRECATED] will be removed in v1 - use `choco outdated` or `cup <pkg|all> -whatif` instead
 * update - [DEPRECATED] RESERVED for future use (you are looking for upgrade, these are not the droids you are looking for)

Please run chocolatey with `choco command -help` for specific help on
 each command.

How To Pass Options / Switches

You can pass options and switches in the following ways:

 * Unless stated otherwise, an option/switch should only be passed one
   time. Otherwise you may find weird/non-supported behavior.
 * `-`, `/`, or `--` (one character switches should not use `--`)
 * **Option Bundling / Bundled Options**: One character switches can be
   bundled. e.g. `-d` (debug), `-f` (force), `-v` (verbose), and `-y`
   (confirm yes) can be bundled as `-dfvy`.
 * NOTE: If `debug` or `verbose` are bundled with local options
   (not the global ones above), some logging may not show up until after
   the local options are parsed.
 * **Use Equals**: You can also include or not include an equals sign
   `=` between options and values.
 * **Quote Values**: When you need to quote an entire argument, such as
   when using spaces, please use a combination of double quotes and
   apostrophes (`"'value'"`). In cmd.exe you can just use double quotes
   (`"value"`) but in powershell.exe you should use backticks
   (`` `"value`" ``) or apostrophes (`'value'`). Using the combination
   allows for both shells to work without issue, except for when the next
   section applies.
 * **Pass quotes in arguments**: When you need to pass quoted values to
   to something like a native installer, you are in for a world of fun. In
   cmd.exe you must pass it like this: `-ia "/yo=""Spaces spaces"""`. In
   PowerShell.exe, you must pass it like this: `-ia '/yo=""Spaces spaces""'`.
   No other combination will work. In PowerShell.exe if you are on version
   v3+, you can try `--%` before `-ia` to just pass the args through as is,
   which means it should not require any special workarounds.
 * **Periods in PowerShell**: If you need to pass a period as part of a
   value or a path, PowerShell doesn't always handle it well. Please
   quote those values using "Quote Values" section above.
 * Options and switches apply to all items passed, so if you are
   installing multiple packages, and you use `--version=1.0.0`, choco
   is going to look for and try to install version 1.0.0 of every
   package passed. So please split out multiple package calls when
   wanting to pass specific options.

Scripting / Integration - Best Practices / Style Guide

When writing scripts, such as PowerShell scripts passing options and
switches, there are some best practices to follow to ensure that you
don't run into issues later. This also applies to integrations that
are calling Chocolatey and parsing output. Chocolatey **uses**
PowerShell, but it is an exe, so it cannot return PowerShell objects.

Following these practices ensures both readability of your scripts AND
compatibility across different versions and editions of Chocolatey.
Following this guide will ensure your experience is not frustrating
based on choco not receiving things you think you are passing to it.

 * For consistency, always use `choco`, not `choco.exe`. Never use
   shortcut commands like `cinst` or `cup`.
 * Always have the command as the first argument to `choco. e.g.
   `choco install`, where `install` is the command.
 * If there is a subcommand, ensure that is the second argument. e.g.
   `choco source list`, where `source` is the command and `list` is the
   subcommand.
 * Typically the subject comes next. If installing packages, the
   subject would be the package names, e.g. `choco install pkg1 pkg2`.
 * Never use 'nupkg' or point directly to a nupkg file UNLESS using
   'choco push'. Use the source folder instead, e.g. `choco install
   <package id> --source="'c:\folder\with\package'"` instead of
   `choco install DoNotDoThis.1.0.nupkg` or `choco install DoNotDoThis
    --source="'c:\folder\with\package\DoNotDoThis.1.0.nupkg'"`.
 * Switches and parameters are called simply options. Options come
   after the subject. e.g. `choco install pkg1 --debug --verbose`.
 * Never use the force option (`--force`/`-f`) in scripts (or really
   otherwise as a default mode of use). Force is an override on
   Chocolatey behavior. If you are wondering why Chocolatey isn't doing
   something like the documentation says it should, it's likely because
   you are using force. Stop.
 * Always use full option name. If the short option is `-n`, and the
   full option is `--name`, use `--name`. The only acceptable short
   option for use in scripts is `-y`. Find option names in help docs
   online or through `choco -?` /`choco [Command Name] -?`.
 * For scripts that are running automated, always use `-y`. Do note
   that even with `-y` passed, some things / state issues detected will
   temporarily stop for input - the key here is temporarily. They will
   continue without requiring any action after the temporary timeout
   (typically 30 seconds).
 * Full option names are prepended with two dashes, e.g. `--` or
   `--debug --verbose --ignore-proxy`.
 * When setting a value to an option, always put an equals (`=`)
   between the name and the setting, e.g. `--source="'local'"`.
 * When setting a value to an option, always surround the value
   properly with double quotes bookending apostrophes, e.g.
   `--source="'internal_server'"`.
 * If you are building PowerShell scripts, you can most likely just
   simply use apostrophes surrounding option values, e.g.
   `--source='internal_server'`.
 * Prefer upgrade to install in scripts. You can't `install` to a newer
   version of something, but you can `choco upgrade` which will do both
   upgrade or install (unless switched off explicitly).
 * If you are sharing the script with others, pass `--source` to be
   explicit about where the package is coming from. Use full link and
   not source name ('https://chocolatey.org/api/v2' versus
   'chocolatey').
 * If parsing output, you might want to use `--limit-output`/`-r` to
   get output in a more machine parseable format. NOTE: Not all
   commands handle return of information in an easily digestible
   output.
 * Use exit codes to determine status. Chocolatey exits with 0 when
   everything worked appropriately and other exits codes like 1 when
   things error. There are package specific exit codes that are
   recommended to be used and reboot indicating exit codes as well. To
   check exit code when using PowerShell, immediately call
   `$exitCode = $LASTEXITCODE` to get the value choco exited with.

Here's an example following bad practices (line breaks added for
 readability):

  `choco install pkg1 -y -params '/Option:Value /Option2:value with
   spaces' --c4b-option 'Yaass' --option-that-is-new 'dude upgrade'`

Now here is that example written with best practices (again line
 breaks added for readability - there are not line continuations
 for choco):

  `choco upgrade pkg1 -y --source="'https://chocolatey.org/api/v2'"
   --package-parameters="'/Option:Value /Option2:value with spaces'"
   --c4b-option="'Yaass'" --option-that-is-new="'dude upgrade'"`

Note the differences between the two:
 * Which is more self-documenting?
 * Which will allow for the newest version of something installed or
   upgraded to (which allows for more environmental consistency on
   packages and versions)?
 * Which may throw an error on a badly passed option?
 * Which will throw errors on unknown option values? See explanation
   below.

Chocolatey ignores options it doesn't understand, but it can only
 ignore option values if they are tied to the option with an
 equals sign ('='). Note those last two options in the examples above?
 If you roll off of a commercial edition or someone with older version
 attempts to run the badly crafted script `--c4b-option 'Yaass'
 --option-that-is-new 'dude upgrade'`, they are likely to see errors on
 'Yaass' and 'dude upgrade' because they are not explicitly tied to the
 option they are written after. Now compare that to the other script.
 Choco will ignore `--c4b-option="'Yaass'"` and
 `--option-that-is-new="'dude upgrade'"` as a whole when it doesn't
 register the options. This means that your script doesn't error.

Following these scripting best practices will ensure your scripts work
 everywhere they are used and with newer versions of Chocolatey.

Default Options and Switches

 -?, --help, -h
     Prints out the help menu.

 -d, --debug
     Debug - Show debug messaging.

 -v, --verbose
     Verbose - Show verbose messaging. Very verbose messaging, avoid using
       under normal circumstances.

     --trace
     Trace - Show trace messaging. Very, very verbose trace messaging. Avoid
       except when needing super low-level .NET Framework debugging. Available
       in 0.10.4+.

     --nocolor, --no-color
     No Color - Do not show colorization in logging output. This overrides
       the feature 'logWithoutColor', set to 'False'. Available in 0.10.9+.

     --acceptlicense, --accept-license
     AcceptLicense - Accept license dialogs automatically. Reserved for
       future use.

 -y, --yes, --confirm
     Confirm all prompts - Chooses affirmative answer instead of prompting.
       Implies --accept-license

 -f, --force
     Force - force the behavior. Do not use force during normal operation -
       it subverts some of the smart behavior for commands.

     --noop, --whatif, --what-if
     NoOp / WhatIf - Don't actually do anything.

 -r, --limitoutput, --limit-output
     LimitOutput - Limit the output to essential information

     --timeout, --execution-timeout=VALUE
     CommandExecutionTimeout (in seconds) - The time to allow a command to
       finish before timing out. Overrides the default execution timeout in the
       configuration of 2700 seconds. '0' for infinite starting in 0.10.4.

 -c, --cache, --cachelocation, --cache-location=VALUE
     CacheLocation - Location for download cache, defaults to %TEMP% or value
       in chocolatey.config file.

     --allowunofficial, --allow-unofficial, --allowunofficialbuild, --allow-unofficial-build
     AllowUnofficialBuild - When not using the official build you must set
       this flag for choco to continue.

     --failstderr, --failonstderr, --fail-on-stderr, --fail-on-standard-error, --fail-on-error-output
     FailOnStandardError - Fail on standard error output (stderr), typically
       received when running external commands during install providers. This
       overrides the feature failOnStandardError.

     --use-system-powershell
     UseSystemPowerShell - Execute PowerShell using an external process
       instead of the built-in PowerShell host. Should only be used when
       internal host is failing. Available in 0.9.10+.

     --no-progress
     Do Not Show Progress - Do not show download progress percentages.
       Available in 0.10.4+.

     --proxy=VALUE
     Proxy Location - Explicit proxy location. Overrides the default proxy
       location of ''. Available for config settings in 0.9.9.9+, this CLI
       option available in 0.10.4+.

     --proxy-user=VALUE
     Proxy User Name - Explicit proxy user (optional). Requires explicity
       proxy (`--proxy` or config setting). Overrides the default proxy user of
       ''. Available for config settings in 0.9.9.9+, this CLI option available
       in 0.10.4+.

     --proxy-password=VALUE
     Proxy Password - Explicit proxy password (optional) to be used with
       username. Requires explicity proxy (`--proxy` or config setting) and
       user name.  Overrides the default proxy password (encrypted in settings
       if set). Available for config settings in 0.9.9.9+, this CLI option
       available in 0.10.4+.

     --proxy-bypass-list=VALUE
     ProxyBypassList - Comma separated list of regex locations to bypass on
       proxy. Requires explicity proxy (`--proxy` or config setting). Overrides
       the default proxy bypass list of ''. Available in 0.10.4+.

     --proxy-bypass-on-local
     Proxy Bypass On Local - Bypass proxy for local connections. Requires
       explicity proxy (`--proxy` or config setting). Overrides the default
       proxy bypass on local setting of 'True'. Available in 0.10.4+.

     --log-file=VALUE
     Log File to output to in addition to regular loggers. Available in 0.1-
       0.8+.
Chocolatey v0.10.15

最重要的是：
巧克力v0.10.15
chocolatey v.0.10.15 message

ok，测试一下是否安装了npm：）

首先写：npm -version
如果返回一个版本，你很好！！！！😊
现在你可以从npm安装了！
例如：我安装tailwindcss

• 转到网站tailwindcss x1c 0d1x
• 复制npm代码
  
  npm install tailwindcss
• 打开VS Code并粘贴它。

PS C：\Users\laaou\Desktop> npm -版本6.14.14
PS C：\Users\laaou\Desktop> npm install tailwindcss npm WARN saveError ENOENT：no such file or directory，open 'C：\Users\laaou\package.json' npm WARN enoent ENOENT：没有这样的文件或目录，打开'C：\Users\laaou\package.json' npm WARN email protected(https://stackoverflow.com/cdn-cgi/l/email-protection)需要autoprefixer@^10.0.2的对等体，但没有安装。您必须自己安装对等依赖项。npm WARN laaou No description npm WARN laaou No repository field. npm WARN laaou没有README数据
npm WARN laaou No license field. npm WARN optional跳过可选依赖性：email protected(https://stackoverflow.com/cdn-cgi/l/email-protection)（node_modules\fsevents）：npm WARN notsup跳过可选依赖：不支持email protected(https://stackoverflow.com/cdn-cgi/l/email-protection)的平台：wanted {“os”：“达尔文”，“arch”：“any”}（current：{“os”：“win32”，“arch”：“x64”}）

• tailwi email protected(https://stackoverflow.com/cdn-cgi/l/email-protection)在3.857秒内更新了1个软件包并审核了180个软件包

17个软件包正在寻找资金运行npm fund了解详细信息
发现0个漏洞
PS C：\Users\laaou\Desktop>

• 然后尝试使用npm基金，如果你是好奇的

我也是。只要安装过程继续进行，我认为这些特定的错误是微不足道的。它可能需要一段时间才能完成，因为它使用了大量的网络和CPU。如果所有的设置过程都完成了，并且终端中的最后一条消息是共享的，那么您可能会用光标暂停它。只需按space或enter，终端将释放。

同样的，当这种情况发生时，关闭窗口，重新启动或做任何其他事情之前，检查CMD中的节点版本，如果下载时出现您选择的版本，一切顺利，如果什么都没有出现，那么如果你应该尝试通过其他方式，有时它会保持这样，因为它不给予一个完整的响应，这就是windows电源 shell 是如何.（它总是发生在我身上）。