I have a package that I manually updated in order to have multiple versions of the same tool running (as explained here).
Now, when I execute npm -g outdated, I am getting the following output:
$ npm -g outdate
npm notice
npm notice New minor version of npm available! 7.18.1 -> 7.20.1
npm notice Changelog: https://github.com/npm/cli/releases/tag/v7.20.1
npm notice Run npm install -g npm#7.20.1 to update!
npm notice
npm ERR! code ENOVERSIONS
npm ERR! No versions available for ask-cli-1
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/b/.npm/_logs/2021-07-24T13_02_50_529Z-debug.log
Here are the contents of the log, edited for brevity:
0 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', '-g', 'update' ]
1 info using npm#7.18.1
2 info using node#v16.4.1
...
9 timing config:load:file:/usr/local/lib/node_modules/ask-cli-1/.npmrc Completed in 0ms
...
33 silly fetch manifest ask-cli-1#*
34 http fetch GET 200 https://registry.npmjs.org/ask-cli-1 38ms (cache hit)
...
40 silly placeDep ROOT ask-cli-1# OK for: want: *
...
316 timing idealTree:node_modules/ask-cli-1 Completed in 0ms
...
1338 verbose stack ask-cli-1: No versions available for ask-cli-1
1338 verbose stack at pickManifest (/usr/local/lib/node_modules/npm/node_modules/npm-pick-manifest/index.js:140:25)
1338 verbose stack at module.exports (/usr/local/lib/node_modules/npm/node_modules/npm-pick-manifest/index.js:187:16)
1338 verbose stack at /usr/local/lib/node_modules/npm/node_modules/pacote/lib/registry.js:118:26
1338 verbose stack at async Arborist.[nodeFromEdge] (/usr/local/lib/node_modules/npm/node_modules/#npmcli/arborist/lib/arborist/build-ideal-tree.js:936:19)
1338 verbose stack at async Arborist.[buildDepStep] (/usr/local/lib/node_modules/npm/node_modules/#npmcli/arborist/lib/arborist/build-ideal-tree.js:882:11)
1338 verbose stack at async Arborist.buildIdealTree (/usr/local/lib/node_modules/npm/node_modules/#npmcli/arborist/lib/arborist/build-ideal-tree.js:218:7)
1338 verbose stack at async Arborist.reify (/usr/local/lib/node_modules/npm/node_modules/#npmcli/arborist/lib/arborist/reify.js:134:5)
1338 verbose stack at async Update.update (/usr/local/lib/node_modules/npm/lib/update.js:72:5)
1339 verbose cwd /usr/local/lib/node_modules/ask-cli-1
1340 verbose Darwin 20.5.0
1341 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "-g" "update"
1342 verbose node v16.4.1
1343 verbose npm v7.18.1
1344 error code ENOVERSIONS
1345 error No versions available for ask-cli-1
1346 verbose exit 1
Is there a way to avoid npm looking for a version of ask-cli-1?
You can't exclude a package with npm outdated.
But I recomemnd this package: check-outdated
In your case npm i -g check-outdated
Then:
check-outdated --ignore-packages ask-cli-1 --columns name,type,current,latest,changes
Related
I'm a graphic student trying to learn something further than classic HTML/CSS.
I want to build the default Next.js app, which you can get by npm create-next-app filename.
It certainly works when npm run dev. I can see the index page on localhost:3000.
But npm run build gets:
% npm run build
> test#0.1.0 build /Users/minori/Documents/portfolio/test
> next build
info - Checking validity of types
Failed to compile.
./pages/index.js
8:7 Error: Missing "key" prop for element in array react/jsx-key
/*almost same messages repeated for every line*/
63:13 Error: Missing "key" prop for element in array react/jsx-key
info - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! test#0.1.0 build: `next build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the test#0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/minori/.npm/_logs/2022-02-25T17_53_21_317Z-debug.log
And here is the debug log:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'build' ]
2 info using npm#6.14.15
3 info using node#v14.17.6
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle test#0.1.0~prebuild: test#0.1.0
6 info lifecycle test#0.1.0~build: test#0.1.0
7 verbose lifecycle test#0.1.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle test#0.1.0~build: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/minori/Documents/portfolio/test/node_modules/.bin:/Users/minori/.npm-global/lib/node_modules/n/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/opt/X11/bin:/Library/Apple/usr/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Users/minori/bin:/opt/osxws/bin:/opt/osxws/sbin
9 verbose lifecycle test#0.1.0~build: CWD: /Users/minori/Documents/portfolio/test
10 silly lifecycle test#0.1.0~build: Args: [ '-c', 'next build' ]
11 silly lifecycle test#0.1.0~build: Returned: code: 1 signal: null
12 info lifecycle test#0.1.0~build: Failed to exec build script
13 verbose stack Error: test#0.1.0 build: `next build`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:400:28)
13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:400:28)
13 verbose stack at maybeClose (internal/child_process.js:1055:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid test#0.1.0
15 verbose cwd /Users/minori/Documents/portfolio/test
16 verbose Darwin 20.3.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
18 verbose node v14.17.6
19 verbose npm v6.14.15
20 error code ELIFECYCLE
21 error errno 1
22 error test#0.1.0 build: `next build`
22 error Exit status 1
23 error Failed at the test#0.1.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
I already tried npm install -g npm-rm -rf node_modules-npm install, re-installing node.js, npm cache clear --force and rm package-lock.json.
Does anyone know what the problem is?
What else can I try now?
It's not you, there is an issue logged with eslint-plugin-react that create-next-app uses, if they haven't already done so (try npm create-next-app again) you can find eslint-plugin-react in your package.json to version 7.29.1
You can see the Vercel team noting the change and the eslint-plugin-react author's responding
https://github.com/yannickcr/eslint-plugin-react/issues/3215#issuecomment-1051115159
In my project, I'm using VueCli for the frontend. Now what I'm trying to do is deploy my project which is in remote server into the actual server. I'm using npm run build command to build the frontend first. But I can't build my project since the following error occurs again and again
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! mobile-h5#0.1.0 build: `vue-cli-service build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the mobile-h5#0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/daisywu/.npm/_logs/2021-09-24T06_13_06_000Z-debug.log
I delete package-lock.json and node_modules,then do npm cache clean --force,then do npm install,Still unable to construct
debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'build' ]
2 info using npm#6.14.9
3 info using node#v14.15.3
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle mobile-h5#0.1.0~prebuild: mobile-h5#0.1.0
6 info lifecycle mobile-h5#0.1.0~build: mobile-h5#0.1.0
7 verbose lifecycle mobile-h5#0.1.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle mobile-h5#0.1.0~build: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/daisywu/Documents/mobile-h5/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
9 verbose lifecycle mobile-h5#0.1.0~build: CWD: /Users/daisywu/Documents/mobile-h5
10 silly lifecycle mobile-h5#0.1.0~build: Args: [ '-c', 'vue-cli-service build' ]
11 silly lifecycle mobile-h5#0.1.0~build: Returned: code: 1 signal: null
12 info lifecycle mobile-h5#0.1.0~build: Failed to exec build script
13 verbose stack Error: mobile-h5#0.1.0 build: `vue-cli-service build`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:315:20)
13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:315:20)
13 verbose stack at maybeClose (internal/child_process.js:1048:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid mobile-h5#0.1.0
15 verbose cwd /Users/daisywu/Documents/mobile-h5
16 verbose Darwin 20.3.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
18 verbose node v14.15.3
19 verbose npm v6.14.9
20 error code ELIFECYCLE
21 error errno 1
22 error mobile-h5#0.1.0 build: `vue-cli-service build`
22 error Exit status 1
23 error Failed at the mobile-h5#0.1.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Please help thank you
The reason is insufficient memory. Update the answer for your reference
Written in package.json
"build": "node --max_old_space_size=4096 node_modules/#vue/cli-service/bin/vue-cli-service.js build --mode development"
do npm run build
Trying to compile theme (named foo) in Prestashop:
cd themes/foo/_dev
npm run build
Get the following error.
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! prestashop-classic-dev-tools#1.0.0 build: `webpack`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the prestashop-classic-dev-tools#1.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-07-02T05_58_35_445Z-debug.log
Here is the log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'build' ]
2 info using npm#6.14.13
3 info using node#v14.17.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle prestashop-classic-dev-tools#1.0.0~prebuild: prestashop-classic-dev-tools#1.0.0
6 info lifecycle prestashop-classic-dev-tools#1.0.0~build: prestashop-classic-dev-tools#1.0.0
7 verbose lifecycle prestashop-classic-dev-tools#1.0.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle prestashop-classic-dev-tools#1.0.0~build: PATH: /usr/lib/node_modules/npm/node_mod$
9 verbose lifecycle prestashop-classic-dev-tools#1.0.0~build: CWD: /var/www/html/themes/foo$
10 silly lifecycle prestashop-classic-dev-tools#1.0.0~build: Args: [ '-c', 'webpack' ]
11 silly lifecycle prestashop-classic-dev-tools#1.0.0~build: Returned: code: 2 signal: null
12 info lifecycle prestashop-classic-dev-tools#1.0.0~build: Failed to exec build script
13 verbose stack Error: prestashop-classic-dev-tools#1.0.0 build: `webpack`
13 verbose stack Exit status 2
13 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle$
13 verbose stack at EventEmitter.emit (events.js:376:20)
13 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle$
13 verbose stack at ChildProcess.emit (events.js:376:20)
13 verbose stack at maybeClose (internal/child_process.js:1055:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid prestashop-classic-dev-tools#1.0.0
15 verbose cwd /var/www/html/themes/foo/_dev
16 verbose Linux 5.8.0-59-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "build"
18 verbose node v14.17.0
19 verbose npm v6.14.13
20 error code ELIFECYCLE
21 error errno 2
22 error prestashop-classic-dev-tools#1.0.0 build: `webpack`
22 error Exit status 2
23 error Failed at the prestashop-classic-dev-tools#1.0.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2, true ]
npm version is:
> npm -v
6.14.13
What could be the cause?
Cause of the issue not found. Resolved with the following commands:
Clean npm cache
> npm cache clean --force
Remove node modules
> rm -rf node_modules package-lock.json
Install npm
> npm install
Run build
> npm run build
I want to try Tailwind CSS but I meet an issue when I launch "npm run build".
The console returns : tailwind command not found. However I successfully installed it.
I upgrade Node and npm.
this error message :
OnePage#1.0.0 build /Users/ted/Documents/Dweb/HTML : CSS/Projets/OnePage
tailwind build src/css/tailwind.css -o dist/css/tailwind.css
sh: tailwind: command not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! OnePage#1.0.0 build: `tailwind build src/css/tailwind.css -o dist/css/tailwind.css`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the OnePage#1.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/ted/.npm/_logs/2019-06-15T18_11_03_382Z-debug.log
iMac-de-Ted:OnePage ted$ sudo npm run start
npm ERR! missing script: start
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/ted/.npm/_logs/2019-06-15T18_13_18_897Z-debug.log
------------------------------------------------------------------
this is my bug log :
info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run',
'build' ] info using npm#6.9.0
3 info using node#v12.4.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle OnePage#1.0.0~prebuild: OnePage#1.0.0
6 info lifecycle OnePage#1.0.0~build: OnePage#1.0.0
7 verbose lifecycle OnePage#1.0.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle OnePage#1.0.0~build: PATH:
/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/ted/Documents/Dweb/HTML
:
CSS/Projets/OnePage/node_modules/.bin:/Library/Frameworks/Python.framework/Versions/3.7/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
9 verbose lifecycle OnePage#1.0.0~build: CWD:
/Users/ted/Documents/Dweb/HTML : CSS/Projets/OnePage
10 silly lifecycle OnePage#1.0.0~build: Args: [ 10 silly lifecycle
'-c',
10 silly lifecycle 'tailwind build src/css/tailwind.css -o
dist/css/tailwind.css' 10 silly lifecycle ]
11 info lifecycle OnePage#1.0.0~build: Failed to exec build script 12
verbose stack Error: OnePage#1.0.0 build: tailwind build
src/css/tailwind.css -o dist/css/tailwind.css
12 verbose stack spawn ENOENT
12 verbose stack at ChildProcess.
(/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack at ChildProcess.emit (events.js:200:13)
12 verbose stack at maybeClose (internal/child_process.js:1021:16)
12 verbose stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:283:5)
13 verbose pkgid OnePage#1.0.0
14 verbose cwd /Users/ted/Documents/Dweb/HTML : CSS/Projets/OnePage
15 verbose Darwin 18.6.0
16 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run"
"build"
17 verbose node v12.4.0
18 verbose npm v6.9.0
19 error file sh
20 error code ELIFECYCLE
21 error errno ENOENT
22 error syscall spawn
23 error OnePage#1.0.0 build: tailwind build src/css/tailwind.css -o
dist/css/tailwind.css
23 error spawn ENOENT
24 error Failed at the OnePage#1.0.0 build script.
24 error This is probably not a problem with npm. There is likely
additional logging output above. 25 verbose exit [ 1, true ]
I created a client project for vue and run npm run serve,
but got this error:
Tried to reinstall node,npm, edited some PATHS, but nothing worked
Version
3.2.1
Node and OS info
Node v10.14.0/ npm 6.4.1
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'serve' ]
2 info using npm#6.4.1
3 info using node#v10.14.0
4 verbose run-script [ 'preserve', 'serve', 'postserve' ]
5 info lifecycle client#0.1.0~preserve: client#0.1.0
6 info lifecycle client#0.1.0~serve: client#0.1.0
7 verbose lifecycle client#0.1.0~serve: unsafe-perm in lifecycle true
8 verbose lifecycle client#0.1.0~serve: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/alexsexotic/Desktop/work/Test - mongod:node/client/node_modules/.bin:/Library/Frameworks/Python.framework/Versions/3.7/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Frameworks/Python.framework/Versions/3.7/bin:/Users/alexsexotic/.npm-global/bin
9 verbose lifecycle client#0.1.0~serve: CWD: /Users/alexsexotic/Desktop/work/Test - mongod:node/client
10 silly lifecycle client#0.1.0~serve: Args: [ '-c', 'vue-cli-service serve' ]
11 info lifecycle client#0.1.0~serve: Failed to exec serve script
12 verbose stack Error: client#0.1.0 serve: `vue-cli-service serve`
12 verbose stack spawn ENOENT
12 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack at ChildProcess.emit (events.js:182:13)
12 verbose stack at maybeClose (internal/child_process.js:962:16)
12 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
13 verbose pkgid client#0.1.0
14 verbose cwd /Users/alexsexotic/Desktop/work/Test - mongod:node/client
15 verbose Darwin 17.2.0
16 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "serve"
17 verbose node v10.14.0
18 verbose npm v6.4.1
19 error file sh
20 error code ELIFECYCLE
21 error errno ENOENT
22 error syscall spawn
23 error client#0.1.0 serve: `vue-cli-service serve`
23 error spawn ENOENT
24 error Failed at the client#0.1.0 serve script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]
You may check your current cli installation and maybe reinstall your vue-cli. Basically, an npx command runs within your project directory. So running npx [whatever] will always use modules installed within your project itself while npm run [whatever] may refer to some globally installed dependencies.
That said, you might also try using yarn. In the past I've also had some trouble running vue-cli through npm so I switched to yarn.
However I can not help you regarding your index.html problem since this may be another issue. But if you've bootstrapped a fresh vue project throughout vue-cli, it should work.
You can try this:
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
It's work for me.