Failed to install packages #441

martixy · 2020-03-04T08:10:56Z

Wanted to try nuxt. Ran yarn create nuxt-app nuxt-test.

It did some stuff, and actually created the directory with some stuff in there, but then spit out the following error:

C:\Users\martixy\AppData\Local\Yarn\Data\global\node_modules\sao\lib\installPackages.js:108
        throw new SAOError(`Failed to install ${packageName} in ${cwd}`)
        ^

SAOError: Failed to install packages in C:\Web\Projects\nuxt-test
    at ChildProcess.<anonymous> (C:\Users\martixy\AppData\Local\Yarn\Data\global\node_modules\sao\lib\installPackages.js:108:15)
    at ChildProcess.emit (events.js:321:20)
    at ChildProcess.cp.emit (C:\Users\martixy\AppData\Local\Yarn\Data\global\node_modules\sao\node_modules\cross-spawn\lib\enoent.js:34:29)
    at maybeClose (internal/child_process.js:1026:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5) {
  __sao: true
}
error Command failed.
Exit code: 1

Environment:
Win10
Node v13.8.0
yarn v1.22.0

The text was updated successfully, but these errors were encountered:

EunChan0817 · 2020-03-12T05:13:50Z

The same problem.

clarkdo · 2020-03-13T11:42:28Z

@martixy @EunChan0817 Can you please provide the choices of your installing ?

martixy · 2020-03-13T12:38:39Z

What the heck? Why close and then ask for information?

Package manager: Yarn
UI Framework: Vuetify
Server framework: None
Nuxt modules: PWA support
Linting tools: ESLint
Test framework: Jest
Rendering mode: SSR
Dev tools: JS Config

clarkdo · 2020-03-13T12:41:43Z

I closed the duplicate issue and track it in one.
Is there any problem as you’ve mentioned they’re same problem?

martixy · 2020-03-13T12:44:49Z

Ah. My bad. It looked like you closed this issue for a bit. Sorry.

clarkdo · 2020-03-13T12:46:08Z

No worries, I’ll prioritize and look into the issue, thanks for the reporting

overbid · 2020-03-16T08:36:45Z

sudo apt-get install g++ build-essential
Before create project is work for me.

ProwlElement · 2020-03-19T10:53:18Z

I have the same issue here.
@overbid what is sudo apt-get install g++ build-essential going to do?

Cheers,
S

overbid · 2020-03-19T10:57:25Z

Install package builder for font in vuetify. I use yarn.

…

On Thu, Mar 19, 2020, 17:53 Sean Corcoran ***@***.***> wrote: I have the same issue here. @overbid <https://github.com/overbid> what is sudo apt-get install g++ build-essential going to do? Cheers, S — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#441 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEBJV7FK5ZV2JGFPPG3IETRIH2SZANCNFSM4LA6X72A> .

ProwlElement · 2020-03-19T11:06:14Z

Ah sorry I use tailwind myself im not sure if this is the issue.

My setup is slightly different but error is the same.

Is this a sudo thing maybe?

my error:

/Users/prowl/.npm/_npx/42099/lib/node_modules/create-nuxt-app/node_modules/sao/lib/installPackages.js:108
throw new SAOError(Failed to install ${packageName} in ${cwd})
^

Error: Failed to install packages in /Users/prowl/Documents/Dev/nuxt/blog
at ChildProcess.ps.on.code (/Users/prowl/.npm/_npx/42099/lib/node_modules/create-nuxt-app/node_modules/sao/lib/installPackages.js:108:15)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Socket.stream.socket.on (internal/child_process.js:346:11)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at Pipe._handle.close [as _onclose] (net.js:557:12)

overbid · 2020-03-19T11:08:34Z

I have same error when use create-nuxt-app but if using yarn it's ok.

…

On Thu, Mar 19, 2020, 18:06 Sean Corcoran ***@***.***> wrote: Ah sorry I use tailwind myself im not sure if this is the issue. My setup is slightly different but error is the same. Is this a sudo thing maybe? my error: /Users/prowl/.npm/_npx/42099/lib/node_modules/create-nuxt-app/node_modules/sao/lib/installPackages.js:108 throw new SAOError(Failed to install ${packageName} in ${cwd}) ^ Error: Failed to install packages in /Users/prowl/Documents/Dev/nuxt/blog at ChildProcess.ps.on.code (/Users/prowl/.npm/_npx/42099/lib/node_modules/create-nuxt-app/node_modules/sao/lib/installPackages.js:108:15) at emitTwo (events.js:126:13) at ChildProcess.emit (events.js:214:7) at maybeClose (internal/child_process.js:925:16) at Socket.stream.socket.on (internal/child_process.js:346:11) at emitOne (events.js:116:13) at Socket.emit (events.js:211:7) at Pipe._handle.close [as _onclose] (net.js:557:12) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#441 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEBJV4JRU37MK62TPKN77TRIH4DJANCNFSM4LA6X72A> .

ProwlElement · 2020-03-19T11:09:26Z

I have heard

npm install --global --production windows-build-tools works on windows

also someone saying you need to install python but I am not sure yet.

I am using yarn, I will try a few other configs to troubleshoot cheers.

S

ProwlElement · 2020-03-19T11:10:18Z

i used npx to create-nuxt-app actually

overbid · 2020-03-19T11:11:12Z

I'm already install python3 too.

…

On Thu, Mar 19, 2020, 18:09 Sean Corcoran ***@***.***> wrote: I have heard npm install --global --production windows-build-tools works on windows also someone saying you need to install python but I am not sure yet. I am using yarn, I will try a few other configs to troubleshoot cheers. S — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#441 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEBJVZB3EZGTY2FGTICDULRIH4PHANCNFSM4LA6X72A> .

chavyleung · 2020-03-27T07:25:08Z

same error

shivgarg5676 · 2020-03-27T10:47:50Z

any update here? I am facing the same error as well.

clarkdo · 2020-03-27T10:57:38Z

@chavyleung @shivgarg5676 Could you provide the steps you reproduce this issue ? It would be very helpful for us to locate the root casue, thanks in advance.

ProwlElement · 2020-03-27T11:04:49Z

upgrade node and yarn to latest versions

yarn create nuxt-app

Simple but worked for me :)

ProwlElement · 2020-03-27T11:06:04Z

yarn create nuxt-app [your-project-name]

clarkdo · 2020-03-27T11:11:31Z

@ProwlElement I'm using node 13 and yarn 1.22, the error doesn't happen to me, is there anything else I need to be aware ?

shivgarg5676 · 2020-03-27T11:14:52Z

I tested using the latest versions of node. node v12.16.1 and v13.12.0. The command I used was npx create-nuxt-app nuxt-css

this is the error log

clarkdo · 2020-03-27T11:17:47Z

@egoist From the stacktrace, it seems to be related to saojs, do you have any idea ?

shivgarg5676 · 2020-03-27T11:23:44Z

Yea, it seems like related to Sao js, but nuxt should take care of this thing as well. At least it should make sure if a user is using everything latest things should work smoothly.

clarkdo · 2020-03-27T11:28:14Z

@shivgarg5676 I understood you point, since I can't reproduce in my local, so the issue may be related to some local os or lib installations, I'm just asking if @egoist has any idea or experience about this issue.

BTW, @nuxt/core-team could you try to reproduce this issue in your env ?

chavyleung · 2020-03-27T11:30:12Z

@shivgarg5676 I understood you point, since I can't reproduce in my local, so the issue may be related to some local os or lib installations, I'm just asking if @egoist has any idea or experience about this issue.

UI Framework: Vuetify

Vuetify，Vuetify，Vuetify
only Vuetify

shivgarg5676 · 2020-03-27T11:32:29Z

After your comment, I deleted my npm cache using npm cache clean --force. Then things worked. Thanks a lot!!. Sorry for wasting your time on my machine specific issue.

clarkdo · 2020-03-27T11:33:22Z

@chavyleung Still can't reproduce and @shivgarg5676 is not installing vuetify as well.

clarkdo · 2020-03-27T11:35:34Z

@shivgarg5676 If you can reproduce it steadily again, please just let me know, I appreciate you very much about all the helpful info you provided, I hope we can find root cause and fix it.

chavyleung · 2020-03-27T14:33:38Z

@shivgarg5676 If you can reproduce it steadily again, please just let me know, I appreciate you very much about all the helpful info you provided, I hope we can find root cause and fix it.

withoutnpm cache clean --force

chavyleung · 2020-03-27T14:35:43Z

chavy-mbp:vscode chavy$ yarn create nuxt-app team
yarn create v1.22.4
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 🔨  Building fresh packages...

success Installed "create-nuxt-app@2.15.0" with binaries:
      - create-nuxt-app
[#####################################################################] 342/342
create-nuxt-app v2.15.0
✨  Generating Nuxt.js project in team
? Project name nuxt-test
? Project description My grand Nuxt.js project
? Author name Chavy
? Choose programming language JavaScript
? Choose the package manager Yarn
? Choose UI framework Vuetify.js
? Choose custom server framework None (Recommended)
? Choose Nuxt.js modules Axios
? Choose linting tools ESLint, Prettier
? Choose test framework None
? Choose rendering mode Universal (SSR)
? Choose development tools jsconfig.json (Recommended for VS Code)
warning nuxt > @nuxt/webpack > cache-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > babel-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > cache-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > babel-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > cache-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > babel-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > hard-source-webpack-plugin > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please 
update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > cache-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > babel-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > hard-source-webpack-plugin > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please 
update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > cache-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > babel-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > hard-source-webpack-plugin > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please 
update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > postcss-url > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdir
p 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack-dev-middleware > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please upda
te to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > cache-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > babel-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > hard-source-webpack-plugin > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please 
update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > postcss-url > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdir
p 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack-dev-middleware > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please upda
te to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > cache-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > babel-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > hard-source-webpack-plugin > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please 
update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > postcss-url > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdir
p 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack-dev-middleware > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please upda
te to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack-bundle-analyzer > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please upd
ate to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.
x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > terser-webpack-plugin > cacache > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Pl
ease update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack > terser-webpack-plugin > cacache > mkdirp@0.5.4: Legacy versions of mkdirp are no longer sup
ported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > @nuxt/babel-preset-app > core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for u
warning nuxt > @nuxt/webpack > cache-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > babel-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > hard-source-webpack-plugin > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please 
update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > postcss-url > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdir
p 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack-dev-middleware > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please upda
te to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack-bundle-analyzer > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please upd
ate to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.
x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > terser-webpack-plugin > cacache > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Pl
ease update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack > terser-webpack-plugin > cacache > mkdirp@0.5.4: Legacy versions of mkdirp are no longer sup
ported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > @nuxt/babel-preset-app > core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for u
warning nuxt > @nuxt/webpack > cache-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > babel-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > hard-source-webpack-plugin > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please 
update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > postcss-url > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdir
p 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack-dev-middleware > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please upda
te to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack-bundle-analyzer > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please upd
ate to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.
x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > terser-webpack-plugin > cacache > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Pl
ease update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack > terser-webpack-plugin > cacache > mkdirp@0.5.4: Legacy versions of mkdirp are no longer sup
ported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > @nuxt/babel-preset-app > core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for u
sage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
warning nuxt > @nuxt/webpack > terser-webpack-plugin > cacache > move-concurrently > mkdirp@0.5.4: Legacy versions of mkdirp are no 
longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack > watchpack > chokidar > fsevents > node-pre-gyp > mkdirp@0.5.4: Legacy versions of mkdirp ar
e no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > cssnano > cssnano-preset-default > postcss-svgo > svgo > mkdirp@0.5.4: Legacy versions of mkdirp are 
no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > terser-webpack-plugin > cacache > move-concurrently > copy-concurrently > mkdirp@0.5.4: Legacy versio
ns of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack > watchpack > chokidar > fsevents > node-pre-gyp > tar > mkdirp@0.5.4: Legacy versions of mkd
irp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning @nuxtjs/eslint-module > eslint-loader > loader-fs-cache > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. P
lease update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning @nuxtjs/eslint-module > eslint-loader > loader-fs-cache > find-cache-dir > mkdirp@0.5.4: Legacy versions of mkdirp are no lo
nger supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning eslint > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API su
rface has changed to use Promises in 1.x.)
warning eslint > file-entry-cache > flat-cache > write > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please upd
ate to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning "@nuxtjs/vuetify > sass-loader@8.0.2" has unmet peer dependency "webpack@^4.36.0 || ^5.0.0".
warning "@nuxtjs/vuetify > vuetify-loader@1.4.3" has unmet peer dependency "vue-template-compiler@^2.5.0".
warning "@nuxtjs/vuetify > vuetify-loader@1.4.3" has unmet peer dependency "webpack@^4.0.0".
warning "@nuxtjs/vuetify > vuetify@2.2.19" has unmet peer dependency "vue@^2.6.4".
warning "@nuxtjs/eslint-config > eslint-plugin-jest > @typescript-eslint/experimental-utils > @typescript-eslint/typescript-estree >
 tsutils@3.17.1" has unmet peer dependency "typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >=
 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".
warning "@nuxtjs/eslint-module > eslint-loader@3.0.3" has unmet peer dependency "webpack@^4.0.0 || ^5.0.0".
warning Error running install script for optional dependency: "/Users/chavy/Works/workspace/vscode/team/node_modules/watchpack/node_
modules/fsevents: Command failed.
Exit code: 1
Command: node-gyp rebuild
Arguments: 
Directory: /Users/chavy/Works/workspace/vscode/team/node_modules/watchpack/node_modules/fsevents
Output:
gyp info it worked if it ends with ok
gyp info using node-gyp@5.1.0
gyp info using node@13.12.0 | darwin | x64
gyp info find Python using Python version 2.7.16 found at \"/System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Pytho
n.app/Contents/MacOS/Python\"
gyp info spawn /System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
gyp info spawn args [
gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/chavy/Works/workspace/vscode/team/node_modules/watchpack/node_modules/fsevents/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/chavy/Library/Caches/node-gyp/13.12.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/Users/chavy/Library/Caches/node-gyp/13.12.0',
gyp info spawn args   '-Dnode_gyp_dir=/usr/local/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/Users/chavy/Library/Caches/node-gyp/13.12.0/<(target_arch)/node.lib',
warning nuxt > @nuxt/webpack > cache-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > babel-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > hard-source-webpack-plugin > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please 
update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > postcss-url > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdir
p 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack-dev-middleware > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please upda
te to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack-bundle-analyzer > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please upd
ate to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.
x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > terser-webpack-plugin > cacache > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Pl
ease update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack > terser-webpack-plugin > cacache > mkdirp@0.5.4: Legacy versions of mkdirp are no longer sup
ported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > @nuxt/babel-preset-app > core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for u
sage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
warning nuxt > @nuxt/webpack > terser-webpack-plugin > cacache > move-concurrently > mkdirp@0.5.4: Legacy versions of mkdirp are no 
longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack > watchpack > chokidar > fsevents > node-pre-gyp > mkdirp@0.5.4: Legacy versions of mkdirp ar
e no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > cssnano > cssnano-preset-default > postcss-svgo > svgo > mkdirp@0.5.4: Legacy versions of mkdirp are 
no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > terser-webpack-plugin > cacache > move-concurrently > copy-concurrently > mkdirp@0.5.4: Legacy versio
ns of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack > watchpack > chokidar > fsevents > node-pre-gyp > tar > mkdirp@0.5.4: Legacy versions of mkd
irp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning @nuxtjs/eslint-module > eslint-loader > loader-fs-cache > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. P
lease update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning @nuxtjs/eslint-module > eslint-loader > loader-fs-cache > find-cache-dir > mkdirp@0.5.4: Legacy versions of mkdirp are no lo
nger supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning eslint > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API su
rface has changed to use Promises in 1.x.)
warning eslint > file-entry-cache > flat-cache > write > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please upd
ate to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning "@nuxtjs/vuetify > sass-loader@8.0.2" has unmet peer dependency "webpack@^4.36.0 || ^5.0.0".
warning "@nuxtjs/vuetify > vuetify-loader@1.4.3" has unmet peer dependency "vue-template-compiler@^2.5.0".
warning "@nuxtjs/vuetify > vuetify-loader@1.4.3" has unmet peer dependency "webpack@^4.0.0".
warning "@nuxtjs/vuetify > vuetify@2.2.19" has unmet peer dependency "vue@^2.6.4".
warning "@nuxtjs/eslint-config > eslint-plugin-jest > @typescript-eslint/experimental-utils > @typescript-eslint/typescript-estree >
 tsutils@3.17.1" has unmet peer dependency "typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >=
 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".
warning "@nuxtjs/eslint-module > eslint-loader@3.0.3" has unmet peer dependency "webpack@^4.0.0 || ^5.0.0".
warning Error running install script for optional dependency: "/Users/chavy/Works/workspace/vscode/team/node_modules/watchpack/node_
modules/fsevents: Command failed.
Exit code: 1
Command: node-gyp rebuild
Arguments: 
Directory: /Users/chavy/Works/workspace/vscode/team/node_modules/watchpack/node_modules/fsevents
Output:
gyp info it worked if it ends with ok
gyp info using node-gyp@5.1.0
gyp info using node@13.12.0 | darwin | x64
gyp info find Python using Python version 2.7.16 found at \"/System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Pytho
n.app/Contents/MacOS/Python\"
gyp info spawn /System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
gyp info spawn args [
gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/chavy/Works/workspace/vscode/team/node_modules/watchpack/node_modules/fsevents/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/chavy/Library/Caches/node-gyp/13.12.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/Users/chavy/Library/Caches/node-gyp/13.12.0',
gyp info spawn args   '-Dnode_gyp_dir=/usr/local/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/Users/chavy/Library/Caches/node-gyp/13.12.0/<(target_arch)/node.lib',
warning nuxt > @nuxt/webpack > cache-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > babel-loader > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdi
rp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > hard-source-webpack-plugin > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please 
update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > postcss-url > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdir
p 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack-dev-middleware > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please upda
te to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack-bundle-analyzer > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please upd
ate to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.
x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > terser-webpack-plugin > cacache > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Pl
ease update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack > terser-webpack-plugin > cacache > mkdirp@0.5.4: Legacy versions of mkdirp are no longer sup
ported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > @nuxt/babel-preset-app > core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for u
sage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
warning nuxt > @nuxt/webpack > terser-webpack-plugin > cacache > move-concurrently > mkdirp@0.5.4: Legacy versions of mkdirp are no 
longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack > watchpack > chokidar > fsevents > node-pre-gyp > mkdirp@0.5.4: Legacy versions of mkdirp ar
e no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > cssnano > cssnano-preset-default > postcss-svgo > svgo > mkdirp@0.5.4: Legacy versions of mkdirp are 
no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > terser-webpack-plugin > cacache > move-concurrently > copy-concurrently > mkdirp@0.5.4: Legacy versio
ns of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning nuxt > @nuxt/webpack > webpack > watchpack > chokidar > fsevents > node-pre-gyp > tar > mkdirp@0.5.4: Legacy versions of mkd
irp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning @nuxtjs/eslint-module > eslint-loader > loader-fs-cache > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. P
lease update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning @nuxtjs/eslint-module > eslint-loader > loader-fs-cache > find-cache-dir > mkdirp@0.5.4: Legacy versions of mkdirp are no lo
nger supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning eslint > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API su
rface has changed to use Promises in 1.x.)
warning eslint > file-entry-cache > flat-cache > write > mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please upd
ate to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning "@nuxtjs/vuetify > sass-loader@8.0.2" has unmet peer dependency "webpack@^4.36.0 || ^5.0.0".
warning "@nuxtjs/vuetify > vuetify-loader@1.4.3" has unmet peer dependency "vue-template-compiler@^2.5.0".
warning "@nuxtjs/vuetify > vuetify-loader@1.4.3" has unmet peer dependency "webpack@^4.0.0".
warning "@nuxtjs/vuetify > vuetify@2.2.19" has unmet peer dependency "vue@^2.6.4".
warning "@nuxtjs/eslint-config > eslint-plugin-jest > @typescript-eslint/experimental-utils > @typescript-eslint/typescript-estree >
 tsutils@3.17.1" has unmet peer dependency "typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >=
 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".
warning "@nuxtjs/eslint-module > eslint-loader@3.0.3" has unmet peer dependency "webpack@^4.0.0 || ^5.0.0".
warning Error running install script for optional dependency: "/Users/chavy/Works/workspace/vscode/team/node_modules/watchpack/node_
modules/fsevents: Command failed.
Exit code: 1
Command: node-gyp rebuild
Arguments: 
Directory: /Users/chavy/Works/workspace/vscode/team/node_modules/watchpack/node_modules/fsevents
Output:
gyp info it worked if it ends with ok
gyp info using node-gyp@5.1.0
gyp info using node@13.12.0 | darwin | x64
gyp info find Python using Python version 2.7.16 found at \"/System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Pytho
n.app/Contents/MacOS/Python\"
gyp info spawn /System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
gyp info spawn args [
gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/chavy/Works/workspace/vscode/team/node_modules/watchpack/node_modules/fsevents/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/chavy/Library/Caches/node-gyp/13.12.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/Users/chavy/Library/Caches/node-gyp/13.12.0',
gyp info spawn args   '-Dnode_gyp_dir=/usr/local/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/Users/chavy/Library/Caches/node-gyp/13.12.0/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/Users/chavy/Works/workspace/vscode/team/node_modules/watchpack/node_modules/fsevents',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.

gyp: No Xcode or CLT version detected!
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
gyp ERR! System Darwin 19.4.0
gyp ERR! command \"/usr/local/bin/node\" \"/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js\" \"rebuild\"
gyp ERR! cwd /Users/chavy/Works/workspace/vscode/team/node_modules/watchpack/node_modules/fsevents
gyp ERR! node -v v13.12.0
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok"
error /Users/chavy/Works/workspace/vscode/team/node_modules/fibers: Command failed.
Exit code: 127
Command: node build.js || nodejs build.js
Arguments: 
Directory: /Users/chavy/Works/workspace/vscode/team/node_modules/fibers
Output:
gyp info it worked if it ends with ok
gyp info using node-gyp@5.1.0
gyp info using node@13.12.0 | darwin | x64
gyp info find Python using Python version 2.7.16 found at "/System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python
.app/Contents/MacOS/Python"
gyp info spawn /System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
gyp info spawn args [
gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/chavy/Works/workspace/vscode/team/node_modules/fibers/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/chavy/Library/Caches/node-gyp/13.12.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/Users/chavy/Library/Caches/node-gyp/13.12.0',
gyp info spawn args   '-Dnode_gyp_dir=/usr/local/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/Users/chavy/Library/Caches/node-gyp/13.12.0/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/Users/chavy/Works/workspace/vscode/team/node_modules/fibers',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.

gyp: No Xcode or CLT version detected!
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
gyp ERR! System Darwin 19.4.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--release"
gyp ERR! cwd /Users/chavy/Works/workspace/vscode/team/node_modules/fibers
gyp ERR! node -v v13.12.0
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok 
node-gyp exited with code: 1
Please make sure you are using a supported platform and node version. If you
would like to compile fibers on this machine please make sure you have setup your
build environment--
Windows + OS X instructions here: https://github.com/nodejs/node-gyp
Ubuntu users please run: `sudo apt-get install g++ build-essential`
RHEL users please run: `yum install gcc-c++` and `yum groupinstall 'Development Tools'` 
Alpine users please run: `sudo apk add python make g++`
/bin/sh: nodejs: command not found

yarn install v1.22.4
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
info This module is OPTIONAL, you can safely ignore this error
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

/Users/chavy/.config/yarn/global/node_modules/sao/lib/installPackages.js:108
        throw new SAOError(`Failed to install ${packageName} in ${cwd}`)
        ^

SAOError: Failed to install packages in /Users/chavy/Works/workspace/vscode/team
    at ChildProcess.<anonymous> (/Users/chavy/.config/yarn/global/node_modules/sao/lib/installPackages.js:108:15)
    at ChildProcess.emit (events.js:315:20)
    at maybeClose (internal/child_process.js:1026:16)
    at Socket.<anonymous> (internal/child_process.js:441:11)
    at Socket.emit (events.js:315:20)
    at Pipe.<anonymous> (net.js:674:12) {
  __sao: true
}
error Command failed.
Exit code: 1
Command: /usr/local/bin/create-nuxt-app
Arguments: team
Directory: /Users/chavy/Works/workspace/vscode
Output:

info Visit https://yarnpkg.com/en/docs/cli/create for documentation about this command.
chavy-mbp:vscode chavy$

clarkdo · 2020-03-27T14:37:51Z

@chavyleung From you screenshot, it seemed your env is lack of some os tools (g++ build-essential ...).

#441 (comment) from @overbid should be helpful.

chavyleung · 2020-03-27T15:04:45Z

lack

Thanks, its work for me

https://github.com/nodejs/node-gyp/blob/master/macOS_Catalina.md#The-acid-test

I did all that and the acid test still does not pass :-(

sudo rm -rf $(xcode-select -print-path) # Enter root password. No output is normal.

sudo rm -rf /Library/Developer/CommandLineTools # Enter root password.

xcode-select --install

If the acid test steps above still does not pass then...

npm explore npm -g -- npm install node-gyp@latest

npm explore npm -g -- npm explore npm-lifecycle -- npm install node-gyp@latest

If the acid test still does not pass then...

Add a comment to Is this an Issue with MACOS catalina? nodejs/node-gyp#1927 so we can improve.

egoist · 2020-03-28T04:29:04Z

That's a yarn/npm install issue, check yarn/npm error log for details

joshuadabejero · 2020-04-20T01:40:20Z

I got error both yarn and npm!

Please help, thank you! Last time yarn is working but now. Both NPM and YARN having same issues.

Anas-Alwindawee · 2020-04-24T11:41:08Z

Hi I have the same issue on WSL Ubuntu LTS, node v12.16.2, npm v6.14.4, below was my choices and the errors I get,

anas@DESKTOP-VENR4M1:~$ npx create-nuxt-app test-nuxt

create-nuxt-app v2.15.0
✨ Generating Nuxt.js project in test-nuxt
? Project name test-nuxt
? Project description My posh Nuxt.js project
? Author name Anas
? Choose programming language JavaScript
? Choose the package manager Npm
? Choose UI framework Vuetify.js
? Choose custom server framework None (Recommended)
? Choose Nuxt.js modules (Press to select, to toggle all, to invert selection)
? Choose linting tools ESLint, Prettier
? Choose test framework None
? Choose rendering mode Single Page App
? Choose development tools jsconfig.json (Recommended for VS Code)
npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm ERR! Unexpected end of JSON input while parsing near '...jdBkOYpTVM3Y085qWei\n'

npm ERR! A complete log of this run can be found in:
npm ERR! /home/anas/.npm/_logs/2020-04-24T11_38_37_366Z-debug.log

/home/anas/.npm/_npx/4182/lib/node_modules/create-nuxt-app/node_modules/sao/lib/installPackages.js:108
throw new SAOError(Failed to install ${packageName} in ${cwd})
^

SAOError: Failed to install packages in /home/anas/test-nuxt
at ChildProcess. (/home/anas/.npm/_npx/4182/lib/node_modules/create-nuxt-app/node_modules/sao/lib/installPackages.js:108:15)
at ChildProcess.emit (events.js:310:20)
at maybeClose (internal/child_process.js:1021:16)
at Socket. (internal/child_process.js:443:11)
at Socket.emit (events.js:310:20)
at Pipe. (net.js:672:12) {
__sao: true
}

joshuadabejero · 2020-04-27T10:47:59Z

Hi I have the same issue on WSL Ubuntu LTS, node v12.16.2, npm v6.14.4, below was my choices and the errors I get,

anas@DESKTOP-VENR4M1:~$ npx create-nuxt-app test-nuxt

create-nuxt-app v2.15.0
✨ Generating Nuxt.js project in test-nuxt
? Project name test-nuxt
? Project description My posh Nuxt.js project
? Author name Anas
? Choose programming language JavaScript
? Choose the package manager Npm
? Choose UI framework Vuetify.js
? Choose custom server framework None (Recommended)
? Choose Nuxt.js modules (Press to select, to toggle all, to invert selection)
? Choose linting tools ESLint, Prettier
? Choose test framework None
? Choose rendering mode Single Page App
? Choose development tools jsconfig.json (Recommended for VS Code)
npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm ERR! Unexpected end of JSON input while parsing near '...jdBkOYpTVM3Y085qWei\n'

npm ERR! A complete log of this run can be found in:
npm ERR! /home/anas/.npm/_logs/2020-04-24T11_38_37_366Z-debug.log

/home/anas/.npm/_npx/4182/lib/node_modules/create-nuxt-app/node_modules/sao/lib/installPackages.js:108
throw new SAOError(Failed to install ${packageName} in ${cwd})
^

SAOError: Failed to install packages in /home/anas/test-nuxt
at ChildProcess. (/home/anas/.npm/_npx/4182/lib/node_modules/create-nuxt-app/node_modules/sao/lib/installPackages.js:108:15)
at ChildProcess.emit (events.js:310:20)
at maybeClose (internal/child_process.js:1021:16)
at Socket. (internal/child_process.js:443:11)
at Socket.emit (events.js:310:20)
at Pipe. (net.js:672:12) {
__sao: true
}

Hey man, I made it work using Yarn. Choose Yarn too as package manager if you use yarn create nuxt-app. Tho still NPM as package manager is not working. Getting that SAOError: ....

Anas-Alwindawee · 2020-04-27T17:16:58Z

Hi I have the same issue on WSL Ubuntu LTS, node v12.16.2, npm v6.14.4, below was my choices and the errors I get,
anas@DESKTOP-VENR4M1:~$ npx create-nuxt-app test-nuxt
create-nuxt-app v2.15.0
✨ Generating Nuxt.js project in test-nuxt
? Project name test-nuxt
? Project description My posh Nuxt.js project
? Author name Anas
? Choose programming language JavaScript
? Choose the package manager Npm
? Choose UI framework Vuetify.js
? Choose custom server framework None (Recommended)
? Choose Nuxt.js modules (Press to select, to toggle all, to invert selection)
? Choose linting tools ESLint, Prettier
? Choose test framework None
? Choose rendering mode Single Page App
? Choose development tools jsconfig.json (Recommended for VS Code)
npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm ERR! Unexpected end of JSON input while parsing near '...jdBkOYpTVM3Y085qWei\n'
npm ERR! A complete log of this run can be found in:
npm ERR! /home/anas/.npm/_logs/2020-04-24T11_38_37_366Z-debug.log
/home/anas/.npm/_npx/4182/lib/node_modules/create-nuxt-app/node_modules/sao/lib/installPackages.js:108
throw new SAOError(Failed to install ${packageName} in ${cwd})
^
SAOError: Failed to install packages in /home/anas/test-nuxt
at ChildProcess. (/home/anas/.npm/_npx/4182/lib/node_modules/create-nuxt-app/node_modules/sao/lib/installPackages.js:108:15)
at ChildProcess.emit (events.js:310:20)
at maybeClose (internal/child_process.js:1021:16)
at Socket. (internal/child_process.js:443:11)
at Socket.emit (events.js:310:20)
at Pipe. (net.js:672:12) {
__sao: true
}

Hey man, I made it work using Yarn. Choose Yarn too as package manager if you use yarn create nuxt-app. Tho still NPM as package manager is not working. Getting that SAOError: ....

Hi, I'll give it try, is there a way to make it work with npm?

BR

overbid · 2020-04-27T17:53:46Z

I think this is is-promise problem now is-promise upgrade to 2.2.1 to fix this problem.

pravinfullstack · 2020-05-09T14:17:04Z

@overbid Any Update on the issue ?? I couldn't fix on my machine. Seems like it's a vuetify issue.
I tried to install Vuetify separately and failed.

artmarydotir · 2020-05-28T09:16:21Z

@maverickpravin its not vuetify issue,
i get the error without adding any ui framework too.

PedroJuan91 · 2020-06-03T00:16:47Z

@chavyleung Still can't reproduce and @shivgarg5676 is not installing vuetify as well.

@clarkdo what version of node and npm you use?

rbastiansch · 2020-06-06T16:34:15Z

I was with the same problem today, when i used the option to install using npm it says me to install peer dependencies "sudo apt-get install g++ build-essential" and then it finally works for me.

begueradj · 2020-06-15T12:33:17Z

sudo apt-get install g++ build-essential
Before create project is work for me.

That worked for me. @overbid

chonlatee · 2020-06-23T12:35:25Z

sudo apt-get install g++ build-essential
Before create project is work for me.

work for me thank you. @overbid

daksamedia · 2020-08-18T05:14:46Z

I found this error

Error: No valid exports main found for '/usr/local/lib/node_modules/create-nuxt-app/node_modules/cac'

What's the problem here?

Things was done :

Update my npm

Install nuxt from NPM

Install create-nuxt from NPM

Nothing is works

octojoerg · 2020-08-24T10:13:23Z

Could resolve the problem by installing node (and npm) via command line. Before node was installed through "Ubuntu-Software", which caused some problems described here.

daksamedia · 2020-08-25T09:59:48Z

Could resolve the problem by installing node (and npm) via command line. Before node was installed through "Ubuntu-Software", which caused some problems described here.

I solved by installing new version of node.js application. Everything works now

adfasa · 2020-08-26T14:27:24Z

i solved. my disk has no space so this errors occur. Everythin works now

yinguangyao · 2020-08-28T15:46:27Z

I solved this by run as follows:

sudo chown -R 501:20 "/Users/[your user name]/.npm"
npx create-nuxt-app xxx

yung-madam · 2020-10-27T13:51:20Z

solved by
nvm deactivate (to be able to uninstall currently running node version)
then nvm uninstall every version of node and installing by nvm install 12

so it was most likely a rights issue

djmin43 · 2021-06-26T01:19:37Z

I had the exact same issue, and I solved it by changing my node version.

My node version was on 16.1, and switched to the LATEST STABLE version which is (14.17.1).

Always check node -v to make sure your actual node version that's active.

ikhidebright · 2022-02-03T13:42:33Z

Updating my Node version solved the issue

ekazda · 2022-03-31T15:50:49Z

This issue is still occurring for me. I'm using an Apple M1 Max laptop (maybe that has something to do with it for me)

I've tried this with yarn, npm and npx and all result in the same issue. I have the LTS version of node.js installed (16.14.2 as of today) and I have updated and cleaned up all of my global npm modules:

corepack@0.10.0
node-gyp@9.0.0
npm@8.5.5

When I run yarn create nuxt-app test-project I end up with the following:

yarn create v1.22.15
warning package.json: No license field
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 🔨  Building fresh packages...
success Installed "create-nuxt-app@4.0.0" with binaries:
      - create-nuxt-app
[#####################################################################] 342/342
create-nuxt-app v4.0.0
✨  Generating Nuxt.js project in test-project
? Project name: test-project
? Programming language: JavaScript
? Package manager: Yarn
? UI framework: Tailwind CSS
? Nuxt.js modules: Axios - Promise based HTTP client, Progressive Web App (PWA),
 Content - Git-based headless CMS
? Linting tools: ESLint, Prettier
? Testing framework: Jest
? Rendering mode: Universal (SSR / SSG)
? Deployment target: Server (Node.js hosting)
? Development tools: jsconfig.json (Recommended for VS Code if you're not using 
typescript)
? Continuous integration: None
? Version control system: Git
warning ../../../package.json: No license field
warning ../../../package.json: No license field
warning ../../../package.json: No license field
warning @nuxt/content > @nuxt/types > @types/webpack > @types/anymatch@3.0.0: Th
is is a stub types definition. anymatch provides its own type definitions, so yo
u do not need this installed.
warning @nuxt/content > @nuxt/types > @types/autoprefixer > @types/browserslist@
4.15.0: This is a stub types definition. browserslist provides its own type defi
nitions, so you do not need this installed.
warning ../../../package.json: No license field
warning @nuxt/content > @nuxt/types > @types/webpack > @types/anymatch@3.0.0: Th
is is a stub types definition. anymatch provides its own type definitions, so yo
u do not need this installed.
warning @nuxt/content > @nuxt/types > @types/autoprefixer > @types/browserslist@
4.15.0: This is a stub types definition. browserslist provides its own type defi
nitions, so you do not need this installed.
warning ../../../package.json: No license field
warning @nuxt/content > @nuxt/types > @types/webpack > @types/anymatch@3.0.0: Th
is is a stub types definition. anymatch provides its own type definitions, so yo
u do not need this installed.
warning @nuxt/content > @nuxt/types > @types/autoprefixer > @types/browserslist@
4.15.0: This is a stub types definition. browserslist provides its own type defi
nitions, so you do not need this installed.
warning @nuxtjs/pwa > jimp-compact@0.16.2: wrong release
warning nuxt > @nuxt/babel-preset-app > core-js@2.6.12: core-js@<3.4 is no longe
r maintained and not recommended for usage due to the number of issues. Because 
of the V8 engine whims, feature detection in old core-js versions could cause a 
slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependen
cies to the actual version of core-js.
warning ../../../package.json: No license field
warning @nuxt/content > @nuxt/types > @types/webpack > @types/anymatch@3.0.0: Th
is is a stub types definition. anymatch provides its own type definitions, so yo
u do not need this installed.
warning @nuxt/content > @nuxt/types > @types/autoprefixer > @types/browserslist@
4.15.0: This is a stub types definition. browserslist provides its own type defi
nitions, so you do not need this installed.
warning @nuxtjs/pwa > jimp-compact@0.16.2: wrong release
warning nuxt > @nuxt/babel-preset-app > core-js@2.6.12: core-js@<3.4 is no longe
r maintained and not recommended for usage due to the number of issues. Because 
of the V8 engine whims, feature detection in old core-js versions could cause a 
slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependen
cies to the actual version of core-js.
warning ../../../package.json: No license field
warning @nuxt/content > @nuxt/types > @types/webpack > @types/anymatch@3.0.0: Th
is is a stub types definition. anymatch provides its own type definitions, so yo
u do not need this installed.
warning @nuxt/content > @nuxt/types > @types/autoprefixer > @types/browserslist@
4.15.0: This is a stub types definition. browserslist provides its own type defi
nitions, so you do not need this installed.
warning @nuxtjs/pwa > jimp-compact@0.16.2: wrong release
warning nuxt > @nuxt/babel-preset-app > core-js@2.6.12: core-js@<3.4 is no longe
r maintained and not recommended for usage due to the number of issues. Because 
of the V8 engine whims, feature detection in old core-js versions could cause a 
slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependen
cies to the actual version of core-js.
warning nuxt > @nuxt/webpack > webpack-hot-middleware > querystring@0.2.1: The q
warning ../../../package.json: No license field
warning @nuxt/content > @nuxt/types > @types/webpack > @types/anymatch@3.0.0: Th
is is a stub types definition. anymatch provides its own type definitions, so yo
u do not need this installed.
warning @nuxt/content > @nuxt/types > @types/autoprefixer > @types/browserslist@
4.15.0: This is a stub types definition. browserslist provides its own type defi
nitions, so you do not need this installed.
warning @nuxtjs/pwa > jimp-compact@0.16.2: wrong release
warning nuxt > @nuxt/babel-preset-app > core-js@2.6.12: core-js@<3.4 is no longe
r maintained and not recommended for usage due to the number of issues. Because 
of the V8 engine whims, feature detection in old core-js versions could cause a 
slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependen
cies to the actual version of core-js.
warning nuxt > @nuxt/webpack > webpack-hot-middleware > querystring@0.2.1: The q
uerystring API is considered Legacy. new code should use the URLSearchParams API
 instead.
warning nuxt > @nuxt/webpack > webpack > node-libs-browser > url > querystring@0
.2.0: The querystring API is considered Legacy. new code should use the URLSearc
hParams API instead.
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > choki
dar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to c
hokidar 3 with 15x fewer dependencies
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > choki
dar > fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using ins
ecure binaries. Upgrade to fsevents 2.
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
warning nuxt > @nuxt/webpack > cssnano > cssnano-preset-default > postcss-svgo >
 svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
warning nuxt > @nuxt/webpack > postcss-preset-env > postcss-color-functional-not
ation > postcss-values-parser > flatten@1.0.3: flatten is deprecated in favor of
 utility frameworks such as lodash.
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve > source-map-url@0.4.1: See https://github.com/lydell/source-map-url#depre
cated
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve > resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve > urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
warning ../../../package.json: No license field
warning @nuxt/content > @nuxt/types > @types/webpack > @types/anymatch@3.0.0: Th
is is a stub types definition. anymatch provides its own type definitions, so yo
u do not need this installed.
warning @nuxt/content > @nuxt/types > @types/autoprefixer > @types/browserslist@
4.15.0: This is a stub types definition. browserslist provides its own type defi
nitions, so you do not need this installed.
warning @nuxtjs/pwa > jimp-compact@0.16.2: wrong release
warning nuxt > @nuxt/babel-preset-app > core-js@2.6.12: core-js@<3.4 is no longe
r maintained and not recommended for usage due to the number of issues. Because 
of the V8 engine whims, feature detection in old core-js versions could cause a 
slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependen
cies to the actual version of core-js.
warning nuxt > @nuxt/webpack > webpack-hot-middleware > querystring@0.2.1: The q
uerystring API is considered Legacy. new code should use the URLSearchParams API
 instead.
warning nuxt > @nuxt/webpack > webpack > node-libs-browser > url > querystring@0
.2.0: The querystring API is considered Legacy. new code should use the URLSearc
hParams API instead.
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > choki
dar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to c
hokidar 3 with 15x fewer dependencies
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > choki
dar > fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using ins
ecure binaries. Upgrade to fsevents 2.
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
warning nuxt > @nuxt/webpack > cssnano > cssnano-preset-default > postcss-svgo >
 svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
warning nuxt > @nuxt/webpack > postcss-preset-env > postcss-color-functional-not
ation > postcss-values-parser > flatten@1.0.3: flatten is deprecated in favor of
 utility frameworks such as lodash.
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve > source-map-url@0.4.1: See https://github.com/lydell/source-map-url#depre
cated
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve > resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve > urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
warning ../../../package.json: No license field
warning @nuxt/content > @nuxt/types > @types/webpack > @types/anymatch@3.0.0: Th
is is a stub types definition. anymatch provides its own type definitions, so yo
u do not need this installed.
warning @nuxt/content > @nuxt/types > @types/autoprefixer > @types/browserslist@
4.15.0: This is a stub types definition. browserslist provides its own type defi
nitions, so you do not need this installed.
warning @nuxtjs/pwa > jimp-compact@0.16.2: wrong release
warning nuxt > @nuxt/babel-preset-app > core-js@2.6.12: core-js@<3.4 is no longe
r maintained and not recommended for usage due to the number of issues. Because 
of the V8 engine whims, feature detection in old core-js versions could cause a 
slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependen
cies to the actual version of core-js.
warning nuxt > @nuxt/webpack > webpack-hot-middleware > querystring@0.2.1: The q
uerystring API is considered Legacy. new code should use the URLSearchParams API
 instead.
warning nuxt > @nuxt/webpack > webpack > node-libs-browser > url > querystring@0
.2.0: The querystring API is considered Legacy. new code should use the URLSearc
hParams API instead.
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > choki
dar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to c
hokidar 3 with 15x fewer dependencies
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > choki
dar > fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using ins
ecure binaries. Upgrade to fsevents 2.
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
warning nuxt > @nuxt/webpack > cssnano > cssnano-preset-default > postcss-svgo >
 svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
warning nuxt > @nuxt/webpack > postcss-preset-env > postcss-color-functional-not
ation > postcss-values-parser > flatten@1.0.3: flatten is deprecated in favor of
 utility frameworks such as lodash.
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve > source-map-url@0.4.1: See https://github.com/lydell/source-map-url#depre
cated
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve > resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve > urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
warning vue-jest > babel-plugin-transform-es2015-modules-commonjs > babel-runtim
e > core-js@2.6.12: core-js@<3.4 is no longer maintained and not recommended for
 usage due to the number of issues. Because of the V8 engine whims, feature dete
ction in old core-js versions could cause a slowdown up to 100x even if nothing 
is polyfilled. Please, upgrade your dependencies to the actual version of core-j
s.
warning vue-jest > extract-from-css > css > source-map-resolve@0.5.3: See https:
//github.com/lydell/source-map-resolve#deprecated
warning vue-jest > extract-from-css > css > urix@0.1.0: Please see https://githu
b.com/lydell/urix#deprecated
warning "nuxt > @nuxt/components@2.2.1" has unmet peer dependency "consola@*".
warning " > @babel/eslint-parser@7.17.0" has unmet peer dependency "@babel/core@
>=7.11.0".
warning "@nuxtjs/eslint-config > eslint-plugin-promise@5.2.0" has incorrect peer
 dependency "eslint@^7.0.0".
warning "@nuxtjs/eslint-config > eslint-config-standard@16.0.3" has incorrect pe
er dependency "eslint@^7.12.1".
warning "@nuxtjs/eslint-config > eslint-plugin-jest > @typescript-eslint/experim
ental-utils > @typescript-eslint/utils > @typescript-eslint/typescript-estree > 
tsutils@3.21.0" has unmet peer dependency "typescript@>=2.8.0 || >= 3.2.0-dev ||
 >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta |
| >= 3.7.0-dev || >= 3.7.0-beta".
warning " > babel-core@7.0.0-bridge.0" has unmet peer dependency "@babel/core@^7
.0.0-0".
warning " > babel-jest@27.5.1" has unmet peer dependency "@babel/core@^7.8.0".
warning "babel-jest > babel-preset-jest@27.5.1" has unmet peer dependency "@babe
l/core@^7.0.0".
warning "babel-jest > babel-preset-jest > babel-preset-current-node-syntax@1.0.1
" has unmet peer dependency "@babel/core@^7.0.0".
warning "babel-jest > babel-preset-jest > babel-preset-current-node-syntax > @ba
bel/plugin-syntax-import-meta@7.10.4" has unmet peer dependency "@babel/core@^7.
0.0-0".
warning "babel-jest > babel-preset-jest > babel-preset-current-node-syntax > @ba
bel/plugin-syntax-bigint@7.8.3" has unmet peer dependency "@babel/core@^7.0.0-0"
.
error /Users/quantumdynamix/QD Shares/Git Shares/test-project/node_modules/deasy
nc: Command failed.
Exit code: 1
Command: node ./build.js
Arguments: 
Directory: /Users/quantumdynamix/QD Shares/Git Shares/test-project/node_modules/
deasync
Output:
gyp info it worked if it ends with ok
gyp info using node-gyp@9.0.0
gyp info using node@16.14.2 | darwin | arm64
gyp info find Python using Python version 3.8.9 found at "/Library/Developer/Com
mandLineTools/usr/bin/python3"
gyp info spawn /Library/Developer/CommandLineTools/usr/bin/python3
gyp info spawn args [
gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp
/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/quantumdynamix/QD Shares/Git Shares/test-project/n
ode_modules/deasync/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/add
on.gypi',
gyp info spawn args   '-I',
gyp info spawn args   
'/Users/quantumdynamix/Library/Caches/node-gyp/16.14.2/include/node/common.gypi'
,
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/Users/quantumdynamix/Library/Caches/node
-gyp/16.14.2',
gyp info spawn args   '-Dnode_gyp_dir=/usr/local/lib/node_modules/npm/node_modul
es/node-gyp',
gyp info spawn args   
'-Dnode_lib_file=/Users/quantumdynamix/Library/Caches/node-gyp/16.14.2/<(target_
arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/Users/quantumdynamix/QD Shares/Git Sha
res/test-project/node_modules/deasync',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
   CXX(target) Release/obj.target/deasync/src/deasync.o
clang: error: no such file or directory: 'Shares/Git'
clang: error: no such file or directory: 'Shares/test-project/node_modules/node-
addon-api'
make: *** [Release/obj.target/deasync/src/deasync.o] Error 1
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_
modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (node:events:526:28)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_p
rocess:291:12)
gyp ERR! System Darwin 21.4.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_mod
ules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/quantumdynamix/QD Shares/Git Shares/test-project/node_module
s/deasync
gyp ERR! node -v v16.14.2
gyp ERR! node-gyp -v v9.0.0
gyp ERR! not ok 
Build failed

yarn install v1.22.15
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this 
command.

/Users/quantumdynamix/.config/yarn/global/node_modules/sao/lib/installPackages.js:108
        throw new SAOError(`Failed to install ${packageName} in ${cwd}`)
        ^

SAOError: Failed to install packages in /Users/quantumdynamix/QD Shares/Git Shares/test-project
    at ChildProcess.<anonymous> (/Users/quantumdynamix/.config/yarn/global/node_modules/sao/lib/installPackages.js:108:15)
    at ChildProcess.emit (node:events:526:28)
    at maybeClose (node:internal/child_process:1092:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {
  __sao: true
}
error Command failed.
Exit code: 1
Command: /usr/local/bin/create-nuxt-app
Arguments: test-project
Directory: /Users/quantumdynamix/QD Shares/Git Shares
Output:

info Visit https://yarnpkg.com/en/docs/cli/create for documentation about this command.```

clarkdo self-assigned this Mar 13, 2020

clarkdo mentioned this issue Mar 13, 2020

When creating a project, selecting Vuetify results in an error. #447

Closed

clarkdo closed this as completed Apr 5, 2020

ekazda mentioned this issue Mar 31, 2022

Failed to install ${packageName} in ${cwd} #948

Open

Failed to install packages #441

Failed to install packages #441

Comments

martixy commented Mar 4, 2020

EunChan0817 commented Mar 12, 2020

clarkdo commented Mar 13, 2020

martixy commented Mar 13, 2020

clarkdo commented Mar 13, 2020

martixy commented Mar 13, 2020

clarkdo commented Mar 13, 2020

overbid commented Mar 16, 2020

ProwlElement commented Mar 19, 2020

overbid commented Mar 19, 2020 via email

ProwlElement commented Mar 19, 2020

overbid commented Mar 19, 2020 via email

ProwlElement commented Mar 19, 2020

ProwlElement commented Mar 19, 2020

overbid commented Mar 19, 2020 via email

chavyleung commented Mar 27, 2020

shivgarg5676 commented Mar 27, 2020

clarkdo commented Mar 27, 2020

ProwlElement commented Mar 27, 2020

ProwlElement commented Mar 27, 2020

clarkdo commented Mar 27, 2020

shivgarg5676 commented Mar 27, 2020

clarkdo commented Mar 27, 2020

shivgarg5676 commented Mar 27, 2020

clarkdo commented Mar 27, 2020 • edited Loading

chavyleung commented Mar 27, 2020

shivgarg5676 commented Mar 27, 2020

clarkdo commented Mar 27, 2020

clarkdo commented Mar 27, 2020

chavyleung commented Mar 27, 2020

chavyleung commented Mar 27, 2020

clarkdo commented Mar 27, 2020

chavyleung commented Mar 27, 2020

I did all that and the acid test still does not pass :-(

egoist commented Mar 28, 2020

joshuadabejero commented Apr 20, 2020

Anas-Alwindawee commented Apr 24, 2020

joshuadabejero commented Apr 27, 2020

Anas-Alwindawee commented Apr 27, 2020

overbid commented Apr 27, 2020

pravinfullstack commented May 9, 2020

artmarydotir commented May 28, 2020 • edited Loading

PedroJuan91 commented Jun 3, 2020

rbastiansch commented Jun 6, 2020 • edited Loading

begueradj commented Jun 15, 2020 • edited Loading

chonlatee commented Jun 23, 2020 • edited Loading

daksamedia commented Aug 18, 2020

octojoerg commented Aug 24, 2020

daksamedia commented Aug 25, 2020

adfasa commented Aug 26, 2020

yinguangyao commented Aug 28, 2020

yung-madam commented Oct 27, 2020 • edited Loading

djmin43 commented Jun 26, 2021

ikhidebright commented Feb 3, 2022

ekazda commented Mar 31, 2022 • edited Loading

clarkdo commented Mar 27, 2020 •

edited

Loading

artmarydotir commented May 28, 2020 •

edited

Loading

rbastiansch commented Jun 6, 2020 •

edited

Loading

begueradj commented Jun 15, 2020 •

edited

Loading

chonlatee commented Jun 23, 2020 •

edited

Loading

yung-madam commented Oct 27, 2020 •

edited

Loading

ekazda commented Mar 31, 2022 •

edited

Loading