Failed to install ${packageName} in ${cwd} #948
Assignees
Labels
Comments
|
Is anyone monitoring these issues? I don't think this is user error and it feels like a pretty critical issue to leave unresolved. Any feedback of any kid would be helpful. |
|
Still having problems with this. I tried upgrading Node.js to 17, and it still happens. |
|
yup i'm getting the same error on node 18 C:\Users\Lemon Rose\Desktop>npx create-nuxt-app melon-nuxt
create-nuxt-app v4.0.0
✨ Generating Nuxt.js project in melon-nuxt
? Project name: melon-nuxt
? Programming language: JavaScript
? Package manager: Yarn
? UI framework: Tailwind CSS
? Nuxt.js modules: (Press <space> to select, <a> to toggle all, <i> to invert selection)
? Linting tools: (Press <space> to select, <a> to toggle all, <i> to invert selection)
? Testing framework: None
? Rendering mode: Universal (SSR / SSG)
? Deployment target: Static (Static/Jamstack hosting)
? Development tools: (Press <space> to select, <a> to toggle all, <i> to invert selection)
? What is your GitHub username? japandotorg
? Version control system: Git
warning nuxt > @nuxt/babel-preset-app > core-js@2.6.12: core-js@<3.23.3 is no longer 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 cau
warning nuxt > @nuxt/babel-preset-app > core-js@2.6.12: core-js@<3.23.3 is no longer 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 cau
warning nuxt > @nuxt/babel-preset-app > core-js@2.6.12: core-js@<3.23.3 is no longer 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 cau
se a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade yo
ur dependencies to the actual version of core-js.
warning nuxt > @nuxt/babel-preset-app > core-js@2.6.12: core-js@<3.23.3 is no longer 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 cau
se a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade yo
ur dependencies to the actual version of core-js.
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > chokidar@2.1.8: Chokidar 2 does not receive
security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > chokidar > fsevents@1.2.13: fsevents 1 will
break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
warning nuxt > @nuxt/webpack > cssnano > cssnano-preset-default > postcss-svgo > svgo@1.3.2: This SVGO version is no lo
nger supported. Upgrade to v2.x.x.
warning nuxt > @nuxt/webpack > postcss-preset-env > postcss-color-functional-notation > 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-resolve@0.5.3: See https://github.com/lyd
ell/source-map-resolve#deprecated
warning nuxt > @nuxt/webpack > webpack > node-libs-browser > url > querystring@0.2.0: The querystring API is considered
Legacy. new code should use the URLSearchParams API instead.
warning nuxt > @nuxt/webpack > cssnano > cssnano-preset-default > postcss-svgo > svgo > stable@0.1.8: Modern JS already
guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://d
eveloper.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-resolve > resolve-url@0.2.1: https://gith
ub.com/lydell/resolve-url#deprecated
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-resolve > source-map-url@0.4.1: See https
://github.com/lydell/source-map-url#deprecated
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-resolve > urix@0.1.0: Please see https://
github.com/lydell/urix#deprecated
error postcss-nesting@8.0.1: The engine "node" is incompatible with this module. Expected version "12 - 16". Got "18.7.
0"
error Found incompatible module.
yarn install v1.22.19
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
C:\Users\Lemon Rose\AppData\Local\npm-cache\_npx\ea7c6e7510ea3309\node_modules\sao\lib\installPackages.js:108
throw new SAOError(`Failed to install ${packageName} in ${cwd}`)
^
SAOError: Failed to install packages in C:\Users\Lemon Rose\Desktop\melon-nuxt
at ChildProcess.<anonymous> (C:\Users\Lemon Rose\AppData\Local\npm-cache\_npx\ea7c6e7510ea3309\node_modules\sao\lib\installPackages.js:108:15)
at ChildProcess.emit (node:events:513:28)
at cp.emit (C:\Users\Lemon Rose\AppData\Local\npm-cache\_npx\ea7c6e7510ea3309\node_modules\sao\node_modules\cross-spawn\lib\enoent.js:34:29)
at maybeClose (node:internal/child_process:1091:16)
at ChildProcess._handle.onexit (node:internal/child_process:302:5) {
__sao: true
}
Node.js v18.7.0 |
|
This should be yarn install issue, can you check yarn error log for the error details ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
create-nuxt-app/4.0.0 darwin-arm64 node-v16.14.2
Steps to reproduce
yarn create nuxt-app test-projectFailed to install ${packageName} in ${cwd})What is Expected?
Expect nuxt-app to be created successfully.
What is actually happening?
This issue is still occurring for me. I'm using an
Apple M1 Maxlaptop (maybe that has something to do with it for me)I've tried this with
yarn,npmandnpxand all result in the same issue. I have the LTS version ofnode.jsinstalled (16.14.2 as of today) and I have updated and cleaned up all of my global npm modules:When I run
yarn create nuxt-app test-projectI end up with the following:The text was updated successfully, but these errors were encountered: