When I intstall npm in Laravel 9 got strange errors - laravel
I try to intstall npm in Laravel 9 site and got strange errors :
npm install
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: bootstrap-switch#3.3.4
npm WARN Found: bootstrap#4.6.2
npm WARN node_modules/bootstrap
npm WARN dev bootstrap#"^4.6.0" from the root project
npm WARN 3 more (admin-lte, bootstrap-colorpicker, tempusdominus-bootstrap-4)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer bootstrap#"^3.1.1" from bootstrap-switch#3.3.4
npm WARN node_modules/bootstrap-switch
npm WARN bootstrap-switch#"3.3.4" from admin-lte#3.2.0
npm WARN node_modules/admin-lte
npm WARN
npm WARN Conflicting peer dependency: bootstrap#3.4.1
npm WARN node_modules/bootstrap
npm WARN peer bootstrap#"^3.1.1" from bootstrap-switch#3.3.4
npm WARN node_modules/bootstrap-switch
npm WARN bootstrap-switch#"3.3.4" from admin-lte#3.2.0
npm WARN node_modules/admin-lte
npm WARN deprecated 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://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated querystring#0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated popper.js#1.16.1: You can find the new Popper v2 at #popperjs/core, this package is dedicated to the legacy v1
npm WARN deprecated flag-icon-css#4.1.7: The project has been renamed to flag-icons
npm notice
npm notice New minor version of npm available! 8.15.0 -> 8.19.1
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.19.1
npm notice Run npm install -g npm#8.19.1 to update!
npm notice
npm ERR! code 1
npm ERR! git dep preparation failed
npm ERR! command /usr/bin/node /usr/lib/node_modules/npm/bin/npm-cli.js install --force --cache=/home/hoster/.npm --prefer-offline=false --prefer-online=false --offline=false --no-progress --no-save --no-audit --include=dev --include=peer --include=optional --no-package-lock-only --no-dry-run
npm ERR! npm WARN using --force Recommended protections disabled.
npm ERR! npm WARN old lockfile
npm ERR! npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm ERR! npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm ERR! npm WARN old lockfile
npm ERR! npm WARN old lockfile This is a one-time fix-up, please be patient...
npm ERR! npm WARN old lockfile
npm ERR! npm WARN old lockfile vue-next: No matching version found for vue-next#3.2.37.
npm ERR! npm WARN old lockfile at module.exports (/usr/lib/node_modules/npm/node_modules/npm-pick-manifest/lib/index.js:209:23)
npm ERR! npm WARN old lockfile at RegistryFetcher.manifest (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:125:22)
npm ERR! npm WARN old lockfile at async Array.<anonymous> (/usr/lib/node_modules/npm/node_modules/#npmcli/arborist/lib/arborist/build-ideal-tree.js:784:9)
npm ERR! npm WARN old lockfile Could not fetch metadata for vue-next#3.2.37 vue-next: No matching version found for vue-next#3.2.37.
npm ERR! npm WARN old lockfile at module.exports (/usr/lib/node_modules/npm/node_modules/npm-pick-manifest/lib/index.js:209:23)
npm ERR! npm WARN old lockfile at RegistryFetcher.manifest (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:125:22)
npm ERR! npm WARN old lockfile at async Array.<anonymous> (/usr/lib/node_modules/npm/node_modules/#npmcli/arborist/lib/arborist/build-ideal-tree.js:784:9) {
npm ERR! npm WARN old lockfile code: 'ETARGET',
npm ERR! npm WARN old lockfile type: 'version',
npm ERR! npm WARN old lockfile wanted: '3.2.37',
npm ERR! npm WARN old lockfile versions: [ '0.0.1' ],
npm ERR! npm WARN old lockfile distTags: { latest: '0.0.1' },
npm ERR! npm WARN old lockfile defaultTag: 'latest'
npm ERR! npm WARN old lockfile }
npm ERR! npm WARN old lockfile HttpErrorGeneral: 404 Not Found - GET https://registry.npmjs.org/vue-next-test-utils - Not found
npm ERR! npm WARN old lockfile at /usr/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/check-response.js:93:15
npm ERR! npm WARN old lockfile at runMicrotasks (<anonymous>)
npm ERR! npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm ERR! npm WARN old lockfile at async RegistryFetcher.packument (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:92:19)
npm ERR! npm WARN old lockfile at async RegistryFetcher.manifest (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:124:23)
npm ERR! npm WARN old lockfile at async Array.<anonymous> (/usr/lib/node_modules/npm/node_modules/#npmcli/arborist/lib/arborist/build-ideal-tree.js:784:9)
npm ERR! npm WARN old lockfile Could not fetch metadata for vue-next-test-utils#2.0.0-rc.16 HttpErrorGeneral: 404 Not Found - GET https://registry.npmjs.org/vue-next-test-utils - Not found
npm ERR! npm WARN old lockfile at /usr/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/check-response.js:93:15
npm ERR! npm WARN old lockfile at runMicrotasks (<anonymous>)
npm ERR! npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm ERR! npm WARN old lockfile at async RegistryFetcher.packument (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:92:19)
npm ERR! npm WARN old lockfile at async RegistryFetcher.manifest (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:124:23)
npm ERR! npm WARN old lockfile at async Array.<anonymous> (/usr/lib/node_modules/npm/node_modules/#npmcli/arborist/lib/arborist/build-ideal-tree.js:784:9) {
npm ERR! npm WARN old lockfile headers: [Object: null prototype] {
npm ERR! npm WARN old lockfile date: [ 'Mon, 12 Sep 2022 12:27:07 GMT' ],
npm ERR! npm WARN old lockfile 'content-type': [ 'application/json' ],
npm ERR! npm WARN old lockfile 'content-length': [ '21' ],
npm ERR! npm WARN old lockfile connection: [ 'keep-alive' ],
npm ERR! npm WARN old lockfile 'cf-ray': [ '7498a2ad69ce9bb0-FRA' ],
npm ERR! npm WARN old lockfile vary: [ 'Accept-Encoding' ],
npm ERR! npm WARN old lockfile server: [ 'cloudflare' ],
npm ERR! npm WARN old lockfile 'x-fetch-attempts': [ '1' ],
npm ERR! npm WARN old lockfile 'x-local-cache-status': [ 'skip' ]
npm ERR! npm WARN old lockfile },
npm ERR! npm WARN old lockfile statusCode: 404,
npm ERR! npm WARN old lockfile code: 'E404',
npm ERR! npm WARN old lockfile method: 'GET',
npm ERR! npm WARN old lockfile uri: 'https://registry.npmjs.org/vue-next-test-utils',
npm ERR! npm WARN old lockfile body: { error: 'Not found' },
npm ERR! npm WARN old lockfile pkgid: 'vue-next-test-utils#2.0.0-rc.16'
npm ERR! npm WARN old lockfile }
npm ERR! npm WARN old lockfile HttpErrorGeneral: 404 Not Found - GET https://registry.npmjs.org/vue-next-rollup-plugin-vue - Not found
npm ERR! npm WARN old lockfile at /usr/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/check-response.js:93:15
npm ERR! npm WARN old lockfile at runMicrotasks (<anonymous>)
npm ERR! npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm ERR! npm WARN old lockfile at async RegistryFetcher.packument (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:92:19)
npm ERR! npm WARN old lockfile at async RegistryFetcher.manifest (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:124:23)
npm ERR! npm WARN old lockfile at async Array.<anonymous> (/usr/lib/node_modules/npm/node_modules/#npmcli/arborist/lib/arborist/build-ideal-tree.js:784:9)
npm ERR! npm WARN old lockfile Could not fetch metadata for vue-next-rollup-plugin-vue#6.0.0 HttpErrorGeneral: 404 Not Found - GET https://registry.npmjs.org/vue-next-rollup-plugin-vue - Not found
npm ERR! npm WARN old lockfile at /usr/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/check-response.js:93:15
npm ERR! npm WARN old lockfile at runMicrotasks (<anonymous>)
npm ERR! npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm ERR! npm WARN old lockfile at async RegistryFetcher.packument (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:92:19)
npm ERR! npm WARN old lockfile at async RegistryFetcher.manifest (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:124:23)
npm ERR! npm WARN old lockfile at async Array.<anonymous> (/usr/lib/node_modules/npm/node_modules/#npmcli/arborist/lib/arborist/build-ideal-tree.js:784:9) {
npm ERR! npm WARN old lockfile headers: [Object: null prototype] {
npm ERR! npm WARN old lockfile date: [ 'Mon, 12 Sep 2022 12:27:07 GMT' ],
npm ERR! npm WARN old lockfile 'content-type': [ 'application/json' ],
npm ERR! npm WARN old lockfile 'content-length': [ '21' ],
npm ERR! npm WARN old lockfile connection: [ 'keep-alive' ],
npm ERR! npm WARN old lockfile 'cf-ray': [ '7498a2adadf0695e-FRA' ],
npm ERR! npm WARN old lockfile vary: [ 'Accept-Encoding' ],
npm ERR! npm WARN old lockfile server: [ 'cloudflare' ],
npm ERR! npm WARN old lockfile 'x-fetch-attempts': [ '1' ],
npm ERR! npm WARN old lockfile 'x-local-cache-status': [ 'skip' ]
npm ERR! npm WARN old lockfile },
...
npm ERR! npm ERR! A complete log of this run can be found in:
npm ERR! npm ERR! /home/hoster/.npm/_logs/2022-09-12T12_26_51_309Z-debug-0.log
npm ERR! A complete log of this run can be found in:
npm ERR! /home/hoster/.npm/_logs/2022-09-12T12_25_43_401Z-debug-0.log
I see messages
7507 error npm WARN old lockfile The package-lock.json file was created with an old version of npm,
and
7507 error npm WARN old lockfile vue-next: No matching version found for vue-next#3.2.37.
7507 error npm WARN old lockfile at module.exports (/usr/lib/node_modules/npm/node_modules/npm-pick-manifest/lib/index.js:209:23)
Before running install command I removed all lock files in root of my project.
hoster#hoster-os:/Project$ node -v
v16.17.0
hoster#hoster-os:/Project$ npm -v
8.15.0
hoster#hoster-os:/Project$ uname -a
Linux hoster-os 5.15.0-41-generic #44~20.04.1-Ubuntu SMP Fri Jun 24 13:27:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
In package.json I have :
{
"private": true,
"scripts": {
"dev": "npm run development",
"development": "mix",
"watch": "mix watch",
"watch-poll": "mix watch -- --watch-options-poll=1000",
"hot": "mix watch --hot",
"prod": "npm run production",
"production": "mix --production"
},
"devDependencies": {
"#fortawesome/fontawesome-free": "^5.15.4",
"#inertiajs/inertia": "^0.10.0",
"#inertiajs/inertia-vue3": "^0.5.1",
"#inertiajs/progress": "^0.2.6",
"#tailwindcss/forms": "^0.4.0",
"#tailwindcss/typography": "^0.5.0",
"#vue/compiler-sfc": "^3.0.5",
"admin-lte": "^3.1.0",
"axios": "^0.25",
"bootstrap": "^4.6.0",
"laravel-echo": "^1.11.7",
"laravel-mix": "^6.0.6",
"lodash": "^4.17.19",
"overlayscrollbars": "^1.13.0",
"popper.js": "^1.16.1",
"postcss": "^8.1.14",
"postcss-import": "^12.0.1",
"pusher-js": "^7.1.0-beta",
"resolve-url-loader": "^5.0.0",
"sass": "^1.49.8",
"sass-loader": "^12.6.0",
"tailwindcss": "^3.0.0",
"vue": "^3.2.30",
"vue-loader": "^16.1.2"
},
"dependencies": {
"#ckeditor/ckeditor5-build-classic": "^32.0.0",
"#ckeditor/ckeditor5-vue": "^2.0.1",
"#vueform/multiselect": "github:vueform/multiselect",
"#vuepic/vue-datepicker": "^3.1.1",
"#vueup/vue-quill": "^1.0.0-beta.8",
"codemirror": "^6.0.1",
"mitt": "^3.0.0",
"quill-better-table": "^1.2.10",
"quill-blot-formatter": "^1.0.5",
"sanitize-html": "^2.7.0",
"vue-color-kit": "^1.0.5",
"vue-final-modal": "^3.4.3",
"vue-upload-component": "^3.1.2",
"vue3-colorpicker": "^2.0.4",
"vuejs-paginate-next": "^1.0.2"
}
}
Why I got this error and how it could be fixed ?
UPDATED INFO:
I try to follow steps in the link, but I still errors :
I removed files composer.lock and package-lock.json from root of the app
I manually deleted subdirectories node_modules and vendor
I run command
composer install
with success
I run command under sudo(otherwise I got access error):
sudo npm install -g npm#8.19.1 to update
with success , but some warnings :
npm WARN deprecated set-value#0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated set-value#0.3.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated set-value#0.3.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated set-value#0.3.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated set-value#0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated set-value#0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated set-value#0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated set-value#0.3.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated set-value#0.3.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated set-value#0.3.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated set-value#0.2.0: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated set-value#0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated set-value#0.3.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
changed 657 packages, and audited 853 packages in 2m
19 packages are looking for funding
run `npm fund` for details
53 vulnerabilities (7 low, 3 moderate, 41 high, 2 critical)
To address issues that do not require attention, run:
npm audit fix
To address all issues possible (including breaking changes), run:
npm audit fix --force
Some issues need review, and may require choosing
a different dependency.
and check npm version :
$ npm -v
8.19.1
clear cache :
npm cache clean --force
npm WARN using --force Recommended protections disabled.
But running npm install I got error again :
hoster#hoster-os:/Project$ npm install
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: bootstrap-switch#3.3.4
npm WARN Found: bootstrap#4.6.2
npm WARN node_modules/bootstrap
npm WARN dev bootstrap#"^4.6.0" from the root project
npm WARN 3 more (admin-lte, bootstrap-colorpicker, tempusdominus-bootstrap-4)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer bootstrap#"^3.1.1" from bootstrap-switch#3.3.4
npm WARN node_modules/bootstrap-switch
npm WARN bootstrap-switch#"3.3.4" from admin-lte#3.2.0
npm WARN node_modules/admin-lte
npm WARN
npm WARN Conflicting peer dependency: bootstrap#3.4.1
npm WARN node_modules/bootstrap
npm WARN peer bootstrap#"^3.1.1" from bootstrap-switch#3.3.4
npm WARN node_modules/bootstrap-switch
npm WARN bootstrap-switch#"3.3.4" from admin-lte#3.2.0
npm WARN node_modules/admin-lte
npm WARN deprecated 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://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated querystring#0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated popper.js#1.16.1: You can find the new Popper v2 at #popperjs/core, this package is dedicated to the legacy v1
npm WARN deprecated flag-icon-css#4.1.7: The project has been renamed to flag-icons
npm ERR! code 1
npm ERR! git dep preparation failed
npm ERR! command /usr/bin/node /usr/lib/node_modules/npm/bin/npm-cli.js install --force --cache=/home/hoster/.npm --prefer-offline=false --prefer-online=false --offline=false --no-progress --no-save --no-audit --include=dev --include=peer --include=optional --no-package-lock-only --no-dry-run
npm ERR! npm WARN using --force Recommended protections disabled.
npm ERR! npm WARN old lockfile
npm ERR! npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm ERR! npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm ERR! npm WARN old lockfile
npm ERR! npm WARN old lockfile This is a one-time fix-up, please be patient...
npm ERR! npm WARN old lockfile
npm ERR! npm WARN old lockfile vue-next: No matching version found for vue-next#3.2.37.
npm ERR! npm WARN old lockfile at module.exports (/usr/lib/node_modules/npm/node_modules/npm-pick-manifest/lib/index.js:209:23)
npm ERR! npm WARN old lockfile at RegistryFetcher.manifest (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:125:22)
npm ERR! npm WARN old lockfile at async Array.<anonymous> (/usr/lib/node_modules/npm/node_modules/#npmcli/arborist/lib/arborist/build-ideal-tree.js:738:24)
npm ERR! npm WARN old lockfile Could not fetch metadata for vue-next#3.2.37 vue-next: No matching version found for vue-next#3.2.37.
npm ERR! npm WARN old lockfile at module.exports (/usr/lib/node_modules/npm/node_modules/npm-pick-manifest/lib/index.js:209:23)
npm ERR! npm WARN old lockfile at RegistryFetcher.manifest (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:125:22)
npm ERR! npm WARN old lockfile at async Array.<anonymous> (/usr/lib/node_modules/npm/node_modules/#npmcli/arborist/lib/arborist/build-ideal-tree.js:738:24) {
npm ERR! npm WARN old lockfile code: 'ETARGET',
npm ERR! npm WARN old lockfile type: 'version',
npm ERR! npm WARN old lockfile wanted: '3.2.37',
npm ERR! npm WARN old lockfile versions: [ '0.0.1' ],
npm ERR! npm WARN old lockfile distTags: { latest: '0.0.1' },
npm ERR! npm WARN old lockfile defaultTag: 'latest'
npm ERR! npm WARN old lockfile }
npm ERR! npm WARN old lockfile HttpErrorGeneral: 404 Not Found - GET https://registry.npmjs.org/vue-next-rollup-plugin-vue - Not found
npm ERR! npm WARN old lockfile at /usr/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/check-response.js:95:15
npm ERR! npm WARN old lockfile at runMicrotasks (<anonymous>)
npm ERR! npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm ERR! npm WARN old lockfile at async RegistryFetcher.packument (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:92:19)
npm ERR! npm WARN old lockfile at async RegistryFetcher.manifest (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:124:23)
npm ERR! npm WARN old lockfile at async Array.<anonymous> (/usr/lib/node_modules/npm/node_modules/#npmcli/arborist/lib/arborist/build-ideal-tree.js:738:24)
npm ERR! npm WARN old lockfile Could not fetch metadata for vue-next-rollup-plugin-vue#6.0.0 HttpErrorGeneral: 404 Not Found - GET https://registry.npmjs.org/vue-next-rollup-plugin-vue - Not found
npm ERR! npm WARN old lockfile at /usr/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/check-response.js:95:15
npm ERR! npm WARN old lockfile at runMicrotasks (<anonymous>)
npm ERR! npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm ERR! npm WARN old lockfile 'content-type': [ 'application/json' ],
npm ERR! npm WARN old lockfile 'content-length': [ '21' ],
npm ERR! npm WARN old lockfile connection: [ 'keep-alive' ],
npm ERR! npm WARN old lockfile 'cf-ray': [ '74c9ec85b945bbb0-FRA' ],
npm ERR! npm WARN old lockfile vary: [ 'Accept-Encoding' ],
npm ERR! npm WARN old lockfile server: [ 'cloudflare' ],
npm ERR! npm WARN old lockfile 'x-fetch-attempts': [ '1' ],
npm ERR! npm WARN old lockfile 'x-local-cache-status': [ 'skip' ]
npm ERR! npm WARN old lockfile },
npm ERR! npm WARN old lockfile statusCode: 404,
npm ERR! npm WARN old lockfile code: 'E404',
npm ERR! npm WARN old lockfile method: 'GET',
npm ERR! npm WARN old lockfile uri: 'https://registry.npmjs.org/vue-next-rollup-plugin-vue',
npm ERR! npm WARN old lockfile body: { error: 'Not found' },
npm ERR! npm WARN old lockfile pkgid: 'vue-next-rollup-plugin-vue#6.0.0'
npm ERR! npm WARN old lockfile }
npm ERR! npm WARN old lockfile HttpErrorGeneral: 404 Not Found - GET https://registry.npmjs.org/vue-prev - Not found
npm ERR! npm WARN old lockfile at /usr/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/check-response.js:95:15
npm ERR! npm WARN old lockfile at runMicrotasks (<anonymous>)
npm ERR! npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm ERR! npm WARN old lockfile at async RegistryFetcher.packument (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:92:19)
npm ERR! npm WARN old lockfile at async RegistryFetcher.manifest (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:124:23)
npm ERR! npm WARN old lockfile at async Array.<anonymous> (/usr/lib/node_modules/npm/node_modules/#npmcli/arborist/lib/arborist/build-ideal-tree.js:738:24)
npm ERR! npm WARN old lockfile Could not fetch metadata for vue-prev#2.7.8 HttpErrorGeneral: 404 Not Found - GET https://registry.npmjs.org/vue-prev - Not found
npm ERR! npm WARN old lockfile at /usr/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/check-response.js:95:15
npm ERR! npm WARN old lockfile at runMicrotasks (<anonymous>)
npm ERR! npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm ERR! npm WARN old lockfile at async RegistryFetcher.packument (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:92:19)
npm ERR! npm WARN old lockfile at async RegistryFetcher.manifest (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:124:23)
npm ERR! npm WARN old lockfile at async Array.<anonymous> (/usr/lib/node_modules/npm/node_modules/#npmcli/arborist/lib/arborist/build-ideal-tree.js:738:24) {
npm ERR! npm WARN old lockfile headers: [Object: null prototype] {
npm ERR! npm WARN old lockfile date: [ 'Sun, 18 Sep 2022 12:00:55 GMT' ],
npm ERR! npm WARN old lockfile 'content-type': [ 'application/json' ],
npm ERR! npm WARN old lockfile 'content-length': [ '21' ],
npm ERR! npm WARN old lockfile connection: [ 'keep-alive' ],
npm ERR! npm WARN old lockfile 'cf-ray': [ '74c9ec86fbe39054-FRA' ],
npm ERR! npm WARN old lockfile vary: [ 'Accept-Encoding' ],
npm ERR! npm WARN old lockfile server: [ 'cloudflare' ],
npm ERR! npm WARN old lockfile 'x-fetch-attempts': [ '1' ],
npm ERR! npm WARN old lockfile 'x-local-cache-status': [ 'skip' ]
npm ERR! npm WARN old lockfile },
npm ERR! npm WARN old lockfile statusCode: 404,
npm ERR! npm WARN old lockfile code: 'E404',
npm ERR! npm WARN old lockfile method: 'GET',
npm ERR! npm WARN old lockfile uri: 'https://registry.npmjs.org/vue-prev',
npm ERR! npm WARN old lockfile body: { error: 'Not found' },
npm ERR! npm WARN old lockfile pkgid: 'vue-prev#2.7.8'
npm ERR! npm WARN old lockfile }
npm ERR! npm WARN old lockfile HttpErrorGeneral: 404 Not Found - GET https://registry.npmjs.org/vue-next-jest - Not found
npm ERR! npm WARN old lockfile at /usr/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/check-response.js:95:15
npm ERR! npm WARN old lockfile at runMicrotasks (<anonymous>)
npm ERR! npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm ERR! npm WARN old lockfile at async RegistryFetcher.packument (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:92:19)
npm ERR! npm WARN old lockfile at async RegistryFetcher.manifest (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:124:23)
npm ERR! npm WARN old lockfile at async Array.<anonymous> (/usr/lib/node_modules/npm/node_modules/#npmcli/arborist/lib/arborist/build-ideal-tree.js:738:24)
npm ERR! npm WARN old lockfile Could not fetch metadata for vue-next-jest#27.0.0 HttpErrorGeneral: 404 Not Found - GET https://registry.npmjs.org/vue-next-jest - Not found
npm ERR! npm WARN old lockfile at /usr/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/check-response.js:95:15
npm ERR! npm WARN old lockfile at runMicrotasks (<anonymous>)
npm ERR! npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm ERR! npm WARN old lockfile at async RegistryFetcher.packument (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:92:19)
npm ERR! npm WARN old lockfile at async RegistryFetcher.manifest (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:124:23)
npm ERR! npm WARN old lockfile at async Array.<anonymous> (/usr/lib/node_modules/npm/node_modules/#npmcli/arborist/lib/arborist/build-ideal-tree.js:738:24) {
npm ERR! npm WARN old lockfile headers: [Object: null prototype] {
npm ERR! npm WARN old lockfile date: [ 'Sun, 18 Sep 2022 12:00:55 GMT' ],
npm ERR! npm WARN old lockfile 'content-type': [ 'application/json' ],
npm ERR! npm WARN old lockfile 'content-length': [ '21' ],
npm ERR! npm WARN old lockfile connection: [ 'keep-alive' ],
npm ERR! npm WARN old lockfile 'cf-ray': [ '74c9ec8859a05c56-FRA' ],
npm ERR! npm WARN old lockfile vary: [ 'Accept-Encoding' ],
npm ERR! npm WARN old lockfile server: [ 'cloudflare' ],
...
npm ERR! npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2
npm ERR! npm ERR! gyp ERR! stack at ChildProcess.onExit (/home/hoster/.npm/_cacache/tmp/git-clonesvo8QA/node_modules/node-gyp/lib/build.js:194:23)
npm ERR! npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:513:28)
npm ERR! npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
npm ERR! npm ERR! gyp ERR! System Linux 5.15.0-41-generic
npm ERR! npm ERR! gyp ERR! command "/usr/bin/node" "/home/hoster/.npm/_cacache/tmp/git-clonesvo8QA/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
npm ERR! npm ERR! gyp ERR! cwd /home/hoster/.npm/_cacache/tmp/git-clonesvo8QA/node_modules/node-sass
npm ERR! npm ERR! gyp ERR! node -v v16.17.0
npm ERR! npm ERR! gyp ERR! node-gyp -v v7.1.2
npm ERR! npm ERR! gyp ERR! not ok
npm ERR! npm ERR! Build failed with error code: 1
npm ERR!
npm ERR! npm ERR! A complete log of this run can be found in:
npm ERR! npm ERR! /home/hoster/.npm/_logs/2022-09-18T12_00_30_495Z-debug-0.log
npm ERR! A complete log of this run can be found in:
npm ERR! /home/hoster/.npm/_logs/2022-09-18T11_58_50_566Z-debug-0.log
7) Again I pay attention at lines in error :
npm ERR! npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm ERR! npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm ERR! npm WARN old lockfile
npm ERR! npm WARN old lockfile This is a one-time fix-up, please be patient...
npm ERR! npm WARN old lockfile
npm ERR! npm WARN old lockfile vue-next: No matching version found for vue-next#3.2.37.
I have deleted package-lock.json file before I run npm install ?
?
Thanks in advance!
Try using Node v14, I had the same issue with Node v16 because that project had some old dependencies, which were deprecated and not workable with the latest version of Node.
Your package-lock.json is not valid.
According to this answer:
The first thing you want to do is update your NPM:
npm install -g npm#8.19.1 to update
After that, delete your package-lock.json & node_modules folder.
Next clear your NPM cache using
npm cache clean --force
and re-install your dependencies with
npm install
You should be able to run npm run dev.
This error means, some package looks for some version of a dependency, but this dependency has been declared with a different version requested by earlier package, it prevents a lot of pitfalls, such as some package use something of overrided version of dependency and deal with deprecations or major incompatibilities. So Npm is protecting you from a painful work.
But you can instruct npm installs everything whatever happens. very not recommended:
npm install --force
it will installs all but there no warranties about all dependencies have correct versions of their dependencies.
Related
Heroku returning Error while running npm install
I'm running the follow command to push my app on Heroku 'git push heroku master', but it returns: -----> Installing binaries engines.node (package.json): 16.13.2 engines.npm (package.json): 8.1.2 Resolving node version 16.13.2... Downloading and installing node 16.13.2... npm 8.1.2 already installed with node -----> Installing dependencies Installing node modules (package.json) npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: paper-kit-2-angular#1.4.0 npm ERR! Found: zone.js#0.11.3 npm ERR! node_modules/zone.js npm ERR! zone.js#"0.11.3" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer zone.js#"~0.10.3" from #angular/core#11.0.4 npm ERR! node_modules/#angular/core npm ERR! #angular/core#"11.0.4" from the root project npm ERR! peer #angular/core#"11.0.4" from #angular/common#11.0.4 npm ERR! node_modules/#angular/common npm ERR! #angular/common#"11.0.4" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See /tmp/npmcache.GEG9a/eresolve-report.txt for a full report. Can anyone help me?
Add your local "node" and "npm" version to package.json. For example I did:
"engines": {
"node": "16.15.1",
"npm": "8.5.5"
},
Apparently for me the "knex" module that I use is not compatible with newer npm (I am not sure).
when i am trying to install npm install gulp -D in cmd prompt there many errors displaying
node verison:v12.4.0
npm verison:6.13.4
laravel:5.8
Build failed with error code: 1
npm WARN The package popper.js is included as both a dev and production depende
cy.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.7 (node_modules\fs
vents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents
1.2.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"
)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass#4.11.0 postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass#4.11.0 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional lo
ging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\CLOUD TIMON\AppData\Roaming\npm-cache_logs\2019-12-31T05
00_45_654Z-debug.log
first try to clean npm cache with : npm cache clean --force then delete node_modules folder completely, then again run npm install. that should solve the problem.
Hyperledger Composer Installation
I have tried installed hyper ledger composer CLI & its development tools but got errors. like the
npm WARN deprecated fs-promise#1.0.0: Use mz or fs-extra^3.0 with Promise Support
npm WARN deprecated crypto#0.0.3: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.
npm WARN deprecated jade#1.11.0: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated transformers#2.1.0: Deprecated, use jstransformer
npm WARN deprecated constantinople#3.0.2: Please update to at least constantinople 3.1.1
npm WARN deprecated nodemailer#2.7.2: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated socks#1.1.9: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm WARN deprecated mailcomposer#4.0.1: This project is unmaintained
npm WARN deprecated buildmail#4.0.1: This project is unmaintained
/root/.nvm/versions/node/v8.10.0/bin/composer -> /root/.nvm/versions/node/v8.10.0/lib/node_modules/composer-cli/cli.js
pkcs11js#1.0.14 install /root/.nvm/versions/node/v8.10.0/lib/node_modules/composer-cli/node_modules/pkcs11js
node-gyp rebuild
sh: 1: node-gyp: Permission denied
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.1.3 (node_modules/composer-cli/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! pkcs11js#1.0.14 install: node-gyp rebuild
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the pkcs11js#1.0.14 install 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/2018-03-24T02_16_27_676Z-debug.log
root#Composer:~# npm install -g composer-rest-server
npm WARN deprecated jade#1.11.0: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated fs-promise#1.0.0: Use mz or fs-extra^3.0 with Promise Support
npm WARN deprecated crypto#0.0.3: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.
npm WARN deprecated constantinople#3.0.2: Please update to at least constantinople 3.1.1
npm WARN deprecated transformers#2.1.0: Deprecated, use jstransformer
npm WARN deprecated nodemailer#2.7.2: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated mailcomposer#4.0.1: This project is unmaintained
npm WARN deprecated socks#1.1.9: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm WARN deprecated buildmail#4.0.1: This project is unmaintained
/root/.nvm/versions/node/v8.10.0/bin/composer-rest-server -> /root/.nvm/versions/node/v8.10.0/lib/node_modules/composer-rest-server/cli.js
pkcs11js#1.0.14 install /root/.nvm/versions/node/v8.10.0/lib/node_modules/composer-rest-server/node_modules/pkcs11js
node-gyp rebuild
sh: 1: node-gyp: Permission denied
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! pkcs11js#1.0.14 install: node-gyp rebuild
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the pkcs11js#1.0.14 install 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/2018-03-24T02_16_58_032Z-debug.log
root#Composer:~# npm install -g generator-hyperledger-composer
npm WARN deprecated fs-promise#1.0.0: Use mz or fs-extra^3.0 with Promise Support
npm WARN deprecated crypto#0.0.3: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.
npm WARN deprecated formatio#1.2.0: This package is unmaintained. Use #sinonjs/formatio instead
pkcs11js#1.0.14 install /root/.nvm/versions/node/v8.10.0/lib/node_modules/generator-hyperledger-composer/node_modules/pkcs11js
node-gyp rebuild
sh: 1: node-gyp: Permission denied
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! pkcs11js#1.0.14 install: node-gyp rebuild
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the pkcs11js#1.0.14 install 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/2018-03-24T02_17_21_569Z-debug.log
Whats the best way or single line command to install the composer on ubuntu ?
the i tried to install the cli as sudo user : got this error :
i tried to install the composer cli as sudo user: got this : "swap#composer:~$ npm install -g composer-cli
npm WARN deprecated fs-promise#1.0.0: Use mz or fs-extra^3.0 with Promise Support
npm WARN deprecated crypto#0.0.3: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.
npm WARN deprecated jade#1.11.0: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated transformers#2.1.0: Deprecated, use jstransformer
npm WARN deprecated constantinople#3.0.2: Please update to at least constantinople 3.1.1
npm WARN deprecated nodemailer#2.7.2: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated socks#1.1.9: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm WARN deprecated mailcomposer#4.0.1: This project is unmaintained
npm WARN deprecated buildmail#4.0.1: This project is unmaintained
/home/swap/.nvm/versions/node/v8.10.0/bin/composer -> /home/swap/.nvm/versions/node/v8.10.0/lib/node_modules/composer-cli/cli.js
pkcs11js#1.0.14 install /home/swap/.nvm/versions/node/v8.10.0/lib/node_modules/composer-cli/node_modules/pkcs11js
node-gyp rebuild
Traceback (most recent call last):
File "/home/swap/.nvm/versions/node/v8.10.0/lib/node_modules/npm/node_modules/npm-lifecycle/node_modules/node-gyp/gyp/gyp_main.py", line 13, in
import gyp
File "/home/swap/.nvm/versions/node/v8.10.0/lib/node_modules/npm/node_modules/npm-lifecycle/node_modules/node-gyp/gyp/pylib/gyp/init.py", line 8, in
import gyp.input
File "/home/swap/.nvm/versions/node/v8.10.0/lib/node_modules/npm/node_modules/npm-lifecycle/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 5, in
from compiler.ast import Const
ImportError: No module named compiler.ast
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/home/swap/.nvm/versions/node/v8.10.0/lib/node_modules/npm/node_modules/npm-lifecycle/node_modules/node-gyp/lib/configure.js:336:16)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Linux 4.4.0-109-generic
gyp ERR! command "/home/swap/.nvm/versions/node/v8.10.0/bin/node" "/home/swap/.nvm/versions/node/v8.10.0/lib/node_modules/npm/node_modules/npm-lifecycle/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/swap/.nvm/versions/node/v8.10.0/lib/node_modules/composer-cli/node_modules/pkcs11js
gyp ERR! node -v v8.10.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.1.3 (node_modules/composer-cli/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! pkcs11js#1.0.14 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the pkcs11js#1.0.14 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
"
please guide
I would run a npm update and take a look at this two links: https://hyperledger.github.io/composer/installing/installing-prereqs and https://hyperledger.github.io/composer/reference/commands.html Read with care about the requisites. And I also notice the information: Please note: When using Ubuntu this command will fail when running in a root user shell.
Laravel npm install on OSX vagrant box gives node-sass error
My package.json file:
{
"private": true,
"devDependencies": {
"babel-polyfill": "^6.9.1",
"gulp": "*",
"laravel-elixir-browsersync2": "*",
"laravel-elixir-vueify": "1.0.3"
},
"dependencies": {
"bootstrap-sass": "*",
"laravel-elixir": "5.0.0"
}
}
I try to do a npm install and I get an error. That seems to be related with node-sass.
Here's the error log:
npm WARN deprecated tough-cookie#2.2.2: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated node-uuid#1.4.7: use uuid module instead
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch#1.0.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch#0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs#1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs#^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN prefer global coffee-script#1.12.1 should be installed with -g
npm WARN prefer global marked#0.3.6 should be installed with -g
npm WARN prefer global node-gyp#3.4.0 should be installed with -g
> node-sass#3.13.0 install /var/www/html/vm.laravel.bng.dev/node_modules/node-sass
> node scripts/install.js
/var/www/html/vm.laravel.bng.dev/node_modules/tough-cookie/lib/pubsuffix.js:96
{"ac":true,"com.ac":true,"edu.ac":true,"gov.ac":true,"net.ac":true,"mil.ac":true,"org.ac":true,"ad":true,"nom.ad":true,"ae":true,"co.ae":true,"net.ae":true,"org.ae":true,"sch.ae":true,"ac.ae":true,"gov.ae":true,"mil.ae":true,"aero":true,"accident-investigation.aero":true,"accident-prevention.aero":true,"aerobatic.aero":true,"aeroclub.aero":true,"aerodrome.aero":true,"agents.aero":true,"aircraft.aero":true,"airline.aero":true,"airport.aero":true,"air-surveillance.aero":true,"airtraffic.aero":true,"air-traffic-control.aero":true,"ambulance.aero":true,"amusement.aero":true,"association.aero":true,"author.aero":true,"ballooning.aero":true,"broker.aero":true,"caa.aero":true,"cargo.aero":true,"catering.aero":true,"certification.aero":true,"championship.aero":true,"charter.aero":true,"civilaviation.aero":true,"club.aero":true,"conference.aero":true,"consultant.aero":true,"consulting.aero":true,"control.aero":true,"council.aero":true,"cr
SyntaxError: Invalid or unexpected token
at Object.exports.runInThisContext (vm.js:76:16)
at Module._compile (module.js:542:28)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (/var/www/html/vm.laravel.bng.dev/node_modules/tough-cookie/lib/cookie.js:34:17)
at Module._compile (module.js:570:32)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.0.15: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.0.0 (node_modules/gulp-watch/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.0.15: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN Error: EPERM: operation not permitted, scandir '/var/www/html/vm.laravel.bng.dev/node_modules/cross-spawn/node_modules'
npm WARN at Error (native)
npm WARN { Error: EPERM: operation not permitted, scandir '/var/www/html/vm.laravel.bng.dev/node_modules/cross-spawn/node_modules'
npm WARN at Error (native)
npm WARN errno: -1,
npm WARN code: 'EPERM',
npm WARN syscall: 'scandir',
npm WARN path: '/var/www/html/vm.laravel.bng.dev/node_modules/cross-spawn/node_modules' }
npm ERR! Linux 3.10.0-327.el7.x86_64
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v6.9.2
npm ERR! npm v4.0.3
npm ERR! code ELIFECYCLE
npm ERR! node-sass#3.13.0 install: `node scripts/install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass#3.13.0 install script 'node scripts/install.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node scripts/install.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs node-sass
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls node-sass
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /var/www/html/vm.laravel.bng.dev/npm-debug.log
From memory, you could try npm rebuild node-sass. Also, if you may run into a problem with symlinks, try npm rebuild node --no-bin-links. Disclaimer: not tested.
npm MongoDB package installation fails on Windows
It says that it's "Not compatible with your operating system or architecture: mongo db#0.9.8". Any ideas? (I have mongo installed and it runs fine) C:\www\webhookit>npm install mongodb npm WARN package.json ejs#0.6.1 No repository field. npm WARN package.json webhookit-comment#0.0.3 No README data npm WARN package.json webhookit-ejs#0.0.3 No README data npm WARN package.json webhookit-http#0.0.5 No README data npm WARN package.json webhookit-jsonparse#0.0.2 No README data npm WARN package.json webhookit-objectbuilder#0.0.3 No README data npm WARN package.json webhookit-jsonpath#0.0.3 No README data npm WARN package.json webhookit-xml2js#0.0.2 No README data npm ERR! notsup Unsupported npm ERR! notsup Not compatible with your operating system or architecture: mongo db#0.9.8 npm ERR! notsup Valid OS: linux,darwin,freebsd npm ERR! notsup Valid Arch: any npm ERR! notsup Actual OS: win32 npm ERR! notsup Actual Arch: ia32 npm ERR! System Windows_NT 6.1.7601 npm ERR! command "C:\\Program Files (x86)\\nodejs\\\\node.exe" "C:\\Program File s (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "mongodb" npm ERR! cwd C:\www\webhookit npm ERR! node -v v0.10.31 npm ERR! npm -v 1.4.23 npm ERR! code EBADPLATFORM npm ERR! npm ERR! Additional logging details can be found in: npm ERR! C:\www\webhookit\npm-debug.log npm ERR! not ok code 0
The package.json of webhookit explicitly states the OS "os": ["darwin", "linux"], Hence you get the error message npm ERR! notsup Valid OS: linux,darwin,freebsd npm ERR! notsup Actual OS: win32 Perhaps you can safely remove that line and the webhookit still function normally without such restriction of OS?