在Node js上安装必要的包时出错

Question

在Node js上安装必要的包时出错

cod*_*ode 26 msbuild powershell installation visual-studio node.js

我在 Windows 上安装 Node.js。安装成功，我还在node.js安装程序中选择了安装必要文件（例如chocolatey）的选项。Node安装完成后，打开Powershell；安装一段时间后，出现以下错误：

# A lot of logs before, just an excerpt
 Microsoft.VisualStudio.Workload.VCTools Microsoft.VisualStudio.Component.Roslyn.Compiler Microsoft.Component.MSBuild Microsoft.VisualStudio.Component.CoreBuildTools Microsoft.VisualStudio.Component.Windows10SDK Microsoft.VisualStudio.Component.VC.CoreBuildTools Microsoft.VisualStudio.Component.Static.Analysis.Tools Microsoft.VisualStudio.Component.VC.Tools.x86.x64 Microsoft.VisualStudio.Component.VC.Redist.14.Latest Microsoft.VisualStudio.Component.Windows10SDK.17763 Microsoft.VisualStudio.Component.VC.CMake.Project Microsoft.VisualStudio.Component.TestTools.BuildTools
[5330:000f][2021-04-19T18:24:09] Decorating UnelevatedProductModifier with UnelevatedInstallerTelemetryDecorator
[5330:000f][2021-04-19T18:24:09] Created a UnelevatedInstallerTelemetryDecorator
[5330:000e][2021-04-19T18:24:09] Download requested: https://aka.ms/vs/15/release/channel
[5330:001d][2021-04-19T18:24:09] Attempting download 'https://aka.ms/vs/15/release/channel' using engine 'WebClient'
[5330:001d][2021-04-19T18:24:09] WebClient error 'RequestCanceled' with 'https://aka.ms/vs/15/release/channel' - GetWebResponse failed along with a cancellation request
[5330:001d][2021-04-19T18:24:09] Error 0x8013153b: [5330:001d][2021-04-19T18:24:09] Could not update channel "https://aka.ms/vs/15/release/channel"
   at System.Threading.CancellationToken.ThrowOperationCanceledException()
   at System.Threading.CancellationToken.ThrowIfCancellationRequested()
   at Microsoft.VisualStudio.Setup.Download.WebClientEngine.GetWebResponse(Uri uri, DownloadContext downloadContext, DownloadSummary& downloadSummary, HttpWebRequest& webRequest, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Setup.Download.WebClientEngine.DownloadCore(Uri uri, Stream stream, ProgressUpdateCallback progress, CancellationToken cancellationToken, DownloadContext downloadContext, ITelemetryOperation telemetryOperation)
   at Microsoft.VisualStudio.Setup.Download.DownloadEngineBase.DownloadWithBitRate(Uri uri, Stream outputStream, ProgressUpdateCallback progress, CancellationToken cancellationToken, DownloadContext downloadContext, ITelemetryOperation telemetryOperation)
   at Microsoft.VisualStudio.Setup.Download.DownloadEngineBase.Download(Uri uri, Stream outputStream, ProgressUpdateCallback progress, CancellationToken cancellationToken, DownloadContext downloadContext, ITelemetryOperation telemetryOperation)
   at Microsoft.VisualStudio.Setup.Download.DownloadManager.DownloadWithRetry(IDownloadEngine[] engines, Uri uri, Stream outputStream, ProgressUpdateCallback progress, CancellationToken cancellationToken, DownloadContext downloadContext, Boolean verifySignature)
   at Microsoft.VisualStudio.Setup.Download.DownloadManager.<>c__DisplayClass23_0.<Download>b__0()
   at System.Threading.Tasks.Task`1.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Setup.ChannelManager.<GetLatestChannelManifestAsync>d__85.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Setup.ChannelManager.<UpdateChannelManifestAsync>d__77.MoveNext()

Run Code Online (Sandbox Code Playgroud)

没有其他事情发生。我该怎么办？

Answer 1

jte*_*r72 28

其他工具会安装许多项目及其依赖项，如在执行脚本时提到的那样。如果需要使用这些工具编译任何节点模块，将使用这些项目。

此脚本将安装编译 Node.js 本机模块所需的 Python 和 Visual Studio 构建工具。请注意，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

Run Code Online (Sandbox Code Playgroud)

特别是 Visualstudio2019-workload-vctools 涉及下载 1.6 GB 的构建工具，这可能需要一段时间。

如果您想知道事情是否有进展，请尝试启动Visual Studio Installer。如果它仍在运行，您可能会收到一条消息，显示“此实例正在运行时无法启动安装程序的另一个实例”。

如果您已退出、重新启动并重新启动脚本，但仍然想知道是否已安装所有工具，您可以执行以下操作：

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

注意：已更新以删除命令-lo中已弃用的内容choco list

Answer 2

Jos*_*eph 12

今天同样的问题。我在为 VS Code（不是 Visual Studio）安装 Node.JS 时，Windows Powershell 停止并冻结了大约 5 分钟。控制台的最后输出是：

$ 创建了一个 UnelevatedInstallerTelemetryDecorator

长话短说：我必须退出终端（不喜欢这个操作）并重新启动计算机，因为安装程序仍在运行。然后我单击安装文件来运行 Node.js 安装向导 (node-v15.14.0-x64.msi)。还有第二个选项可以修复安装尝试：“修复”。单击该按钮，安装向导将完成修复并完全退出。该程序注意到某些元素尚未完成。然后您可以在 VS Code 的终端上运行 javascript 文件。

我不需要修复 VS Code。

从 VS Code 终端运行示例（终端输入以粗体显示）

PS“驱动器位置”\JavaScript>节点 canDrinkNoIfs.js

要在 VSC 中运行脚本，我需要打开文件夹（文件 -> 打开文件夹。），然后创建一个 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"
    }]}

Run Code Online (Sandbox Code Playgroud)

Answer 3

小智 12

it happens to me.

\n

first try to use space or tab. in my first stop powershell

\n

Download of vs_BuildTools.exe (1.4 MB) completed.\nHashes match.\nInstalling visualstudio2017buildtools...\n

Run Code Online (Sandbox Code Playgroud)\n

is working...

\n

\n
guys if you use space or tab, and then work: this happens because you use the click-mouse in the PowerShell, don\'t do this, sometimes is pausing the program :) [if is working, is a normal error, and it don\'t cause nothing danger for completing the downloading]
\n

\n

but then I have a lot of white text.\nthe last stop is

\n

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

Run Code Online (Sandbox Code Playgroud)\n

here the error you have.\xe2\x9d\x8c

\n

for correct this error... do this!

\n

go to edge (or the browser you choose for download)
go to download tab, where there is node-v14.17.5-x64.msi (for edge is CTRL+J)
OPEN FILE
CLICK REPAIR\nand that\'s it

\n

i will put some photos of final result if you need it:

\n

final result SUCCESS\xe2\x9c\x85

\n

EDIT

\n

After a while i have this, in the same powershell i have the first stop.

\n

Chocolatey timed out waiting for the command to finish. The timeout\n specified (or the default value) was \'2700\' seconds. Perhaps try a\n higher `--execution-timeout`? See `choco -h` for details.\n  visualstudio2017-workload-vctools may be able to be automatically uninstalled.\nThe upgrade of visualstudio2017-workload-vctools was NOT successful.\nError while running \'C:\\ProgramData\\chocolatey\\lib\\visualstudio2017-workload-vctools\\tools\\ChocolateyInstall.ps1\'.\n See log for details.\n\nChocolatey upgraded 15/17 packages. 2 packages failed.\n See the log for details (C:\\ProgramData\\chocolatey\\logs\\chocolatey.log).\n\nUpgraded:\n - chocolatey-dotnetfx.extension v1.0.1\n - kb3033929 v1.0.5\n - visualstudio2017buildtools v15.9.38.0\n - chocolatey-windowsupdate.extension v1.0.4\n - vcredist140 v14.29.30133\n - kb2999226 v1.0.20181019\n - visualstudio-installer v2.0.1\n - kb2919355 v1.0.20160915\n - chocolatey-core.extension v1.3.5.1\n - kb2919442 v1.0.20160915\n - chocolatey-visualstudio.extension v1.9.0\n - vcredist2015 v14.0.24215.20170201\n - dotnetfx v4.8.0.20190930\n - kb3035131 v1.0.3\n - python v3.9.6\n\nFailures\n - python3 (exited 1603) - Error while running \'C:\\ProgramData\\chocolatey\\lib\\python3\\tools\\chocolateyInstall.ps1\'.\n See log for details.\n - visualstudio2017-workload-vctools (exited -1) - Error while running \'C:\\ProgramData\\chocolatey\\lib\\visualstudio2017-workload-vctools\\tools\\ChocolateyInstall.ps1\'.\n See log for details.\n

Run Code Online (Sandbox Code Playgroud)\n

and the last thing is TYPE ENTER FOR EXIT - message on powershell

\n

if you see the last message.

\n

See "choco -h" for details.\nso, i write it, in PowerShell.

\n

i have this result, with a green message, in the end, with the version

\n

This is a listing of all of the different things you can pass to choco.\n\nCommands\n\n * list - lists remote or local packages\n * find - searches remote or local packages (alias for search)\n * search - searches remote or local packages (alias for list)\n * info - retrieves package information. Shorthand for choco search pkgname --exact --verbose\n * install - installs packages from various sources\n * pin - suppress upgrades for a package\n * outdated - retrieves packages that are outdated. Similar to upgrade all --noop\n * upgrade - upgrades packages from various sources\n * uninstall - uninstalls a package\n * pack - packages up a nuspec to a compiled nupkg\n * push - pushes a compiled nupkg\n * new - generates files necessary for a chocolatey package from a template\n * sources - view and configure default sources (alias for source)\n * source - view and configure default sources\n * config - Retrieve and configure config file settings\n * feature - view and configure choco features\n * features - view and configure choco features (alias for feature)\n * setapikey - retrieves, saves or deletes an apikey for a particular source (alias for apikey)\n * apikey - retrieves, saves or deletes an apikey for a particular source\n * unpackself - have chocolatey set itself up\n * version - [DEPRECATED] will be removed in v1 - use `choco outdated` or `cup <pkg|all> -whatif` instead\n * update - [DEPRECATED] RESERVED for future use (you are looking for upgrade, these are not the droids you are looking for)\n\n\nPlease run chocolatey with `choco command -help` for specific help on\n each command.\n\nHow To Pass Options / Switches\n\nYou can pass options and switches in the following ways:\n\n * Unless stated otherwise, an option/switch should only be passed one\n   time. Otherwise you may find weird/non-supported behavior.\n * `-`, `/`, or `--` (one character switches should not use `--`)\n * **Option Bundling / Bundled Options**: One character switches can be\n   bundled. e.g. `-d` (debug), `-f` (force), `-v` (verbose), and `-y`\n   (confirm yes) can be bundled as `-dfvy`.\n * NOTE: If `debug` or `verbose` are bundled with local options\n   (not the global ones above), some logging may not show up until after\n   the local options are parsed.\n * **Use Equals**: You can also include or not include an equals sign\n   `=` between options and values.\n * **Quote Values**: When you need to quote an entire argument, such as\n   when using spaces, please use a combination of double quotes and\n   apostrophes (`"\'value\'"`). In cmd.exe you can just use double quotes\n   (`"value"`) but in powershell.exe you should use backticks\n   (`` `"value`" ``) or apostrophes (`\'value\'`). Using the combination\n   allows for both shells to work without issue, except for when the next\n   section applies.\n * **Pass quotes in arguments**: When you need to pass quoted values to\n   to something like a native installer, you are in for a world of fun. In\n   cmd.exe you must pass it like this: `-ia "/yo=""Spaces spaces"""`. In\n   PowerShell.exe, you must pass it like this: `-ia \'/yo=""Spaces spaces""\'`.\n   No other combination will work. In PowerShell.exe if you are on version\n   v3+, you can try `--%` before `-ia` to just pass the args through as is,\n   which means it should not require any special workarounds.\n * **Periods in PowerShell**: If you need to pass a period as part of a\n   value or a path, PowerShell doesn\'t always handle it well. Please\n   quote those values using "Quote Values" section above.\n * Options and switches apply to all items passed, so if you are\n   installing multiple packages, and you use `--version=1.0.0`, choco\n   is going to look for and try to install version 1.0.0 of every\n   package passed. So please split out multiple package calls when\n   wanting to pass specific options.\n\nScripting / Integration - Best Practices / Style Guide\n\nWhen writing scripts, such as PowerShell scripts passing options and\nswitches, there are some best practices to follow to ensure that you\ndon\'t run into issues later. This also applies to integrations that\nare calling Chocolatey and parsing output. Chocolatey **uses**\nPowerShell, but it is an exe, so it cannot return PowerShell objects.\n\nFollowing these practices ensures both readability of your scripts AND\ncompatibility across different versions and editions of Chocolatey.\nFollowing this guide will ensure your experience is not frustrating\nbased on choco not receiving things you think you are passing to it.\n\n * For consistency, always use `choco`, not `choco.exe`. Never use\n   shortcut commands like `cinst` or `cup`.\n * Always have the command as the first argument to `choco. e.g.\n   `choco install`, where `install` is the command.\n * If there is a subcommand, ensure that is the second argument. e.g.\n   `choco source list`, where `source` is the command and `list` is the\n   subcommand.\n * Typically the subject comes next. If installing packages, the\n   subject would be the package names, e.g. `choco install pkg1 pkg2`.\n * Never use \'nupkg\' or point directly to a nupkg file UNLESS using\n   \'choco push\'. Use the source folder instead, e.g. `choco install\n   <package id> --source="\'c:\\folder\\with\\package\'"` instead of\n   `choco install DoNotDoThis.1.0.nupkg` or `choco install DoNotDoThis\n    --source="\'c:\\folder\\with\\package\\DoNotDoThis.1.0.nupkg\'"`.\n * Switches and parameters are called simply options. Options come\n   after the subject. e.g. `choco install pkg1 --debug --verbose`.\n * Never use the force option (`--force`/`-f`) in scripts (or really\n   otherwise as a default mode of use). Force is an override on\n   Chocolatey behavior. If you are wondering why Chocolatey isn\'t doing\n   something like the documentation says it should, it\'s likely because\n   you are using force. Stop.\n * Always use full option name. If the short option is `-n`, and the\n   full option is `--name`, use `--name`. The only acceptable short\n   option for use in scripts is `-y`. Find option names in help docs\n   online or through `choco -?` /`choco [Command Name] -?`.\n * For scripts that are running automated, always use `-y`. Do note\n   that even with `-y` passed, some things / state issues detected will\n   temporarily stop for input - the key here is temporarily. They will\n   continue without requiring any action after the temporary timeout\n   (typically 30 seconds).\n * Full option names are prepended with two dashes, e.g. `--` or\n   `--debug --verbose --ignore-proxy`.\n * When setting a value to an option, always put an equals (`=`)\n   between the name and the setting, e.g. `--source="\'local\'"`.\n * When setting a value to an option, always surround the value\n   properly with double quotes bookending apostrophes, e.g.\n   `--source="\'internal_server\'"`.\n * If you are building PowerShell scripts, you can most likely just\n   simply use apostrophes surrounding option values, e.g.\n   `--source=\'internal_server\'`.\n * Prefer upgrade to install in scripts. You can\'t `install` to a newer\n   version of something, but you can `choco upgrade` which will do both\n   upgrade or install (unless switched off explicitly).\n * If you are sharing the script with others, pass `--source` to be\n   explicit about where the package is coming from. Use full link and\n   not source name (\'https://chocolatey.org/api/v2\' versus\n   \'chocolatey\').\n * If parsing output, you might want to use `--limit-output`/`-r` to\n   get output in a more machine parseable format. NOTE: Not all\n   commands handle return of information in an easily digestible\n   output.\n * Use exit codes to determine status. Chocolatey exits with 0 when\n   everything worked appropriately and other exits codes like 1 when\n   things error. There are package specific exit codes that are\n   recommended to be used and reboot indicating exit codes as well. To\n   check exit code when using PowerShell, immediately call\n   `$exitCode = $LASTEXITCODE` to get the value choco exited with.\n\nHere\'s an example following bad practices (line breaks added for\n readability):\n\n  `choco install pkg1 -y -params \'/Option:Value /Option2:value with\n   spaces\' --c4b-option \'Yaass\' --option-that-is-new \'dude upgrade\'`\n\nNow here is that example written with best practices (again line\n breaks added for readability - there are not line continuations\n for choco):\n\n  `choco upgrade pkg1 -y --source="\'https://chocolatey.org/api/v2\'"\n   --package-parameters="\'/Option:Value /Option2:value with spaces\'"\n   --c4b-option="\'Yaass\'" --option-that-is-new="\'dude upgrade\'"`\n\nNote the differences between the two:\n * Which is more self-documenting?\n * Which will allow for the newest version of something installed or\n   upgraded to (which allows for more environmental consistency on\n   packages and versions)?\n * Which may throw an error on a badly passed option?\n * Which will throw errors on unknown option values? See explanation\n   below.\n\nChocolatey ignores options it doesn\'t understand, but it can only\n ignore option values if they are tied to the option with an\n equals sign (\'=\'). Note those last two options in the examples above?\n If you roll off of a commercial edition or someone with older version\n attempts to run the badly crafted script `--c4b-option \'Yaass\'\n --option-that-is-new \'dude upgrade\'`, they are likely to see errors on\n \'Yaass\' and \'dude upgrade\' because they are not explicitly tied to the\n option they are written after. Now compare that to the other script.\n Choco will ignore `--c4b-option="\'Yaass\'"` and\n `--option-that-is-new="\'dude upgrade\'"` as a whole when it doesn\'t\n register the options. This means that your script doesn\'t error.\n\nFollowing these scripting best practices will ensure your scripts work\n everywhere they are used and with newer versions of Chocolatey.\n\n\nDefault Options and Switches\n\n -?, --help, -h\n     Prints out the help menu.\n\n -d, --debug\n     Debug - Show debug messaging.\n\n -v, --verbose\n     Verbose - Show verbose messaging. Very verbose messaging, avoid using\n       under normal circumstances.\n\n     --trace\n     Trace - Show trace messaging. Very, very verbose trace messaging. Avoid\n       except when needing super low-level .NET Framework debugging. Available\n       in 0.10.4+.\n\n     --nocolor, --no-color\n     No Color - Do not show colorization in logging output. This overrides\n       the feature \'logWithoutColor\', set to \'False\'. Available in 0.10.9+.\n\n     --acceptlicense, --accept-license\n     AcceptLicense - Accept license dialogs automatically. Reserved for\n       future use.\n\n -y, --yes, --confirm\n     Confirm all prompts - Chooses affirmative answer instead of prompting.\n       Implies --accept-license\n\n -f, --force\n     Force - force the behavior. Do not use force during normal operation -\n       it subverts some of the smart behavior for commands.\n\n     --noop, --whatif, --what-if\n     NoOp / WhatIf - Don\'t actually do anything.\n\n -r, --limitoutput, --limit-output\n     LimitOutput - Limit the output to essential information\n\n     --timeout, --execution-timeout=VALUE\n     CommandExecutionTimeout (in seconds) - The time to allow a command to\n       finish before timing out. Overrides the default execution timeout in the\n       configuration of 2700 seconds. \'0\' for infinite starting in 0.10.4.\n\n -c, --cache, --cachelocation, --cache-location=VALUE\n     CacheLocation - Location for download cache, defaults to %TEMP% or value\n       in chocolatey.config file.\n\n     --allowunofficial, --allow-unofficial, --allowunofficialbuild, --allow-unofficial-build\n     AllowUnofficialBuild - When not using the official build you must set\n       this flag for choco to continue.\n\n     --failstderr, --failonstderr, --fail-on-stderr, --fail-on-standard-error, --fail-on-error-output\n     FailOnStandardError - Fail on standard error output (stderr), typically\n       received when running external commands during install providers. This\n       overrides the feature failOnStandardError.\n\n     --use-system-powershell\n     UseSystemPowerShell - Execute PowerShell using an external process\n       instead of the built-in PowerShell host. Should only be used when\n       internal host is failing. Available in 0.9.10+.\n\n     --no-progress\n     Do Not Show Progress - Do not show download progress percentages.\n       Available in 0.10.4+.\n\n     --proxy=VALUE\n     Proxy Location - Explicit proxy location. Overrides the default proxy\n       location of \'\'. Available for config settings in 0.9.9.9+, this CLI\n       option available in 0.10.4+.\n\n     --proxy-user=VALUE\n     Proxy User Name - Explicit proxy user (optional). Requires explicity\n       proxy (`--proxy` or config setting). Overrides the default proxy user of\n       \'\'. Available for config settings in 0.9.9.9+, this CLI option available\n       in 0.10.4+.\n\n     --proxy-password=VALUE\n     Proxy Password - Explicit proxy password (optional) to be used with\n       username. Requires explicity proxy (`--proxy` or config setting) and\n       user name.  Overrides the default proxy password (encrypted in settings\n       if set). Available for config settings in 0.9.9.9+, this CLI option\n       available in 0.10.4+.\n\n     --proxy-bypass-list=VALUE\n     ProxyBypassList - Comma separated list of regex locations to bypass on\n       proxy. Requires explicity proxy (`--proxy` or config setting). Overrides\n       the default proxy bypass list of \'\'. Available in 0.10.4+.\n\n     --proxy-bypass-on-local\n     Proxy Bypass On Local - Bypass proxy for local connections. Requires\n       explicity proxy (`--proxy` or config setting). Overrides the default\n       proxy bypass on local setting of \'True\'. Available in 0.10.4+.\n\n     --log-file=VALUE\n     Log File to output to in addition to regular loggers. Available in 0.1-\n       0.8+.\nChocolatey v0.10.15\n

Run Code Online (Sandbox Code Playgroud)\n

the most important thing is:

\n`Chocolatey v0.10.15`

\n

chocolatey v.0.10.15 message

\n

ok, let test if npm is installed :)

\n

first at all write: npm -version

\n

if return a version, you are fine!!!!

\n

now you can install from npm!

\n

for example: me installing tailwindcss

\n

go to website of tailwindcss
\n
copy the npm code npm install tailwindcss
\n
go to vs code and paste it.
\n
PS C:\\Users\\laaou\\Desktop> npm -version\n6.14.14
\nPS C:\\Users\\laaou\\Desktop> npm install tailwindcss\nnpm WARN saveError ENOENT: no such file or directory, open \'C:\\Users\\laaou\\package.json\'\nnpm WARN enoent ENOENT: no such file or directory, open \'C:\\Users\\laaou\\package.json\'\nnpm WARN tailwindcss@2.2.7 requires a peer of autoprefixer@^10.0.2 but none is installed. You must install peer dependencies yourself.\nnpm WARN laaou No description\nnpm WARN laaou No repository field.\nnpm WARN laaou No README data
\nnpm WARN laaou No license field.\nnpm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules\\fsevents):\nnpm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
\n