I am new to Vue. I had successfully created projects for a while now, with no issues. However, today I created a new project, and when I tried “npm run serve” I got back three errors out of nowhere.
Even old projects that were serving fine, I cant serve them again
I am using windows 7, so the node version is 13.14.0
This is the error I get:
ERROR Failed to compile with 3 errors
10:46:02 PM
ERROR Failed to compile with 3 errors
10:46:02 PM
These dependencies were not found:
* C:\Users\hp\Documents\vue full learn\dojo-blog-
composition\node_modules\webpack-dev-server\client\index.js?
http://192.168.43.35:8081&sockPath=/sockjs-node in multi
(webpack)-dev-server/client?
http://192.168.43.35:8081&sockPath=/sockjs-node
(webpack)/hot/dev-server.js ./src/main.js
* C:\Users\hp\Documents\vue full learn\dojo-blog-
composition\node_modules\webpack\hot\dev-server.js in multi
(webpack)-dev-server/client?
http://192.168.43.35:8081&sockPath=/sockjs-node
(webpack)/hot/dev-server.js ./src/main.js
To install them, you can run: npm install --save
C:\Users\hp\Documents\vue full learn\dojo-blog-
composition\node_modules\webpack-dev-
server\client\index.js?
http://192.168.43.35:8081&sockPath=/sockjs-node
C:\Users\hp\Documents\vue full learn\dojo-blog-
composition\node_modules\webpack\hot\dev-server.js
This relative module was not found:
* ./src/main.js in multi (webpack)-dev-server/client?
http://192.168.43.35:8081&sockPath=/sockjs-node
(webpack)/hot/dev-server.js ./src/main.js
I checked and the webpack-dev-server is in the node-bundles folder.
when I tried installing as directed above, I got more errors:
npm ERR! code ENOLOCAL
npm ERR! Could not install from "..\..\..\Documents\vue" as it
does not contain a package.json file.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\hp\AppData\Roaming\npm-
cache\_logs\2021-01-02T22_03_20_183Z-debug.log
'sockPath' is not recognized as an internal or external command,
operable program or batch file.
This is the package.json
{
"name": "project-planner",
"version": "0.1.0",
"private": true,
"scripts": {
"serve": "vue-cli-service serve",
"build": "vue-cli-service build"
},
"dependencies": {
"core-js": "^3.6.5",
"vue": "^3.0.0",
"vue-router": "^4.0.0-0"
},
"devDependencies": {
"#vue/cli-plugin-babel": "~4.5.0",
"#vue/cli-plugin-router": "~4.5.0",
"#vue/cli-service": "~4.5.0",
"#vue/compiler-sfc": "^3.0.0",
"webpack-dev-server": "^3.11.2"
}
}
I get this with I use npm install
npm WARN deprecated #hapi/joi#15.1.1: Switch to 'npm install joi'
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated chokidar#2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated #hapi/bourne#1.3.2: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated #hapi/hoek#8.5.1: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated #hapi/address#2.1.4: Moved to 'npm install #sideway/address'
npm WARN deprecated #hapi/topo#3.1.6: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated har-validator#5.1.5: this library is no longer supported
npm WARN deprecated fsevents#1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
> core-js#3.8.3 postinstall C:\Users\hp\My Documents\webdev\projects\learnVue\project-planner\node_modules\core-js
> node -e "try{require('./postinstall')}catch(e){}"
Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock
Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
> ejs#2.7.4 postinstall C:\Users\hp\My Documents\webdev\projects\learnVue\project-planner\node_modules\ejs
> node ./postinstall.js
Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/)
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#~2.3.1 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.3.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.2.7 (node_modules\watchpack-chokidar2\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.2.7 (node_modules\webpack-dev-server\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})
added 1214 packages from 934 contributors and audited 1217 packages in 527.888s
61 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
Related
After installing packages using npm install webpack webpack-cli webpack-dev-server --save-dev
The terminal gives me this error message:
➜ Projeto npm install webpack webpack-cli webpack-dev-server --save-dev
npm WARN deprecated chokidar#2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated fsevents#1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.2.7 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN projeto#1.0.0 No description
npm WARN projeto#1.0.0 No repository field.
+ webpack-dev-server#3.11.2
+ webpack-cli#4.7.0
+ webpack#5.38.1
updated 3 packages and audited 499 packages in 35.305s
1 package is looking for funding
run `npm fund` for details
found 1 moderate severity vulnerability
run `npm audit fix` to fix them, or `npm audit` for details
➜ Projeto material-ui
zsh: command not found: material-ui
➜ Projeto npm install # material-ui / core
npm WARN deprecated material-ui#0.20.2: You can now upgrade to #material-ui/core
npm ERR! code EINVALIDTAGNAME
npm ERR! Invalid tag name "#": Tags may not have any characters that encodeURIComponent encodes.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/peter/.npm/_logs/2021-06-02T04_35_32_632Z-debug.log
Because you typed
npm install # material-ui / core
instead of
npm install #material-ui/core
npm went and tried to install the packages #, material-ui, / and core. Because # on its own is an invalid tag name, it threw that error. To undo what you've done, you need to execute:
npm uninstall material-ui core
and then
npm install #material-ui/core --save-dev
While installing Jest with npm I received the following warnings. I would like to know in general what they mean:
npm install --save-dev jest
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated request-promise-native#1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator#5.1.5: this library is no longer supported
npm WARN saveError ENOENT: no such file or directory, open '/home/burtrandpaulie/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^2.1.2 (node_modules/jest-haste-map/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN enoent ENOENT: no such file or directory, open '/home/burtrandpaulie/package.json'
npm WARN burtrandpaulie No description
npm WARN burtrandpaulie No repository field.
npm WARN burtrandpaulie No README data
npm WARN burtrandpaulie No license field.
+ jest#26.6.3
added 520 packages from 355 contributors and audited 521 packages in 61.729s
24 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
All the ones prior to the last 4 are related to dependencies of jest. There are some packages jest uses that have announced they are deprecating, but at this point they are still in wide use (e.g. request) so you can inquire with the jest project what their plan is, but while deprecated the request module will likely be around a while.
The last 4 lines are about your own package.json:
npm WARN burtrandpaulie No description
npm WARN burtrandpaulie No repository field.
npm WARN burtrandpaulie No README data
npm WARN burtrandpaulie No license field.
which just says your package.json doesn't have that info. Nothing crazy or required esp. if you're just starting a project.
I created a Laravel 5.8 project, and I want to install npm. So I typed npm install but I get this message:
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 urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated chokidar#2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated fsevents#1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.2.7 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN notsup Unsupported engine for watchpack-chokidar2#2.0.0: wanted: {"node":"<8.10.0"} (current: {"node":"12.18.3","npm":"6.14.6"})
npm WARN notsup Not compatible with your version of node/npm: watchpack-chokidar2#2.0.0
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#~2.1.2 (node_modules\watchpack\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
added 1055 packages from 500 contributors and audited 1058 packages in 149.498s
37 packages are looking for funding
run `npm fund` for details
found 1 low severity vulnerability
run `npm audit fix` to fix them, or `npm audit` for details
So I saw this question related to my question, and he said run the npm install #popperjs/core --save command and after that npm uninstall popper.js --save in order to install Popper.
But as soon as I typed npm install #popperjs/core --save, I get this message:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.13 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#2.1.3 (node_modules\watchpack\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
+ #popperjs/core#2.5.2
added 1 package from 1 contributor and audited 1059 packages in 9.5s
38 packages are looking for funding
run `npm fund` for details
found 1 low severity vulnerability
run `npm audit fix` to fix them, or `npm audit` for details
So now I don't know really what should I do for installing npm, so if you know, please let me know, I would appreciate that!
Thanks in advance...
UPDATE #1:
Here is my package.json:
{
"private": true,
"scripts": {
"dev": "npm run development",
"development": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
"watch": "npm run development -- --watch",
"watch-poll": "npm run watch -- --watch-poll",
"hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js",
"prod": "npm run production",
"production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"
},
"devDependencies": {
"axios": "^0.19",
"bootstrap": "^4.1.0",
"cross-env": "^5.1",
"jquery": "^3.2",
"laravel-mix": "^4.0.7",
"lodash": "^4.17.13",
"popper.js": "^1.12",
"resolve-url-loader": "^2.3.1",
"sass": "^1.15.2",
"sass-loader": "^7.1.0",
"vue": "^2.5.17"
},
"dependencies": {
"#popperjs/core": "^2.5.2"
}
}
UPDATE 2:
I removed "popper.js": "^1.12", at package.json and node_modules folder and typed npm install but again I get the same error!
Remove "popper.js": "^1.12", line from package.json
then remove node_modules
then run cmd npm install
I'm following a course online and have downloaded Node and NPM.
I have done a package.json file and are have some problems with
the installation.
I really don't understand the error message. I had the latest
version of Node, I tried to downgrade the version to 6.10.3 (the same version in the online course) but I still don't work.
Is there someone here that knows what the problem can be? I'm new at this and not so experienced with the error messages.
{
"author": "Erika",
"description": "Jewelry Shop",
"private": true,
"dependencies": {
"gulp": "~4.0.0",
"laravel-elixir": "~5.0.0"
}
}
$ npm install
npm WARN deprecated babel-preset-es2015#6.24.1: 🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
npm WARN deprecated gulp-util#3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
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 browserslist#0.4.0: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
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 hoek#2.16.3: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated boom#2.10.1: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated cryptiles#2.0.5: This version is no longer maintained. Please upgrade to the latest version.
node-sass#3.13.1 install C:\httpdocs\ecommerce\node_modules\node-sass
node scripts/install.js
Cached binary found at C:\Users\Erika\AppData\Roaming\npm-cache\node-sass\3.13.1\win32-x64-48_binding.node
node-sass#3.13.1 postinstall C:\httpdocs\ecommerce\node_modules\node-sass
node scripts/build.js
Binary found at C:\httpdocs\ecommerce\node_modules\node-sass\vendor\win32-x64-48\binding.node
Testing binary
Binary is fine
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN acorn-dynamic-import#4.0.0 requires a peer of acorn#^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.4 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
added 1299 packages from 772 contributors and audited 17546 packages in 89.815s
found 11 vulnerabilities (8 moderate, 2 high, 1 critical)
run npm audit fix to fix them, or npm audit for details
Which portion of this message log are you concerned about?
It seems like it added the packages for you:
added 1299 packages from 772 contributors and audited 17546 packages in 89.815s
It just had some warnings displayed as well. The warnings may key in to potential issues when running whatever program you are trying to run afterwards, however, without any specific issue, you are probably fine.
The deprecated and unsupported warnings can be possibly fixed by installing the latest versions of the packages that you are using, but there is no guarantee that the package maintainers have updated their dependencies to suit.
To upgrade a package and save it you can use the following command:
npm -i --save gulp#latest laravel-elixir#latest
-i for install, --save to save this back in your dependencies in your package.json.
I'm having trouble installing webpack dev with the following command: npm i --save-dev webpack
Webpack is installed succesfully on my computer as npm i webpack -g #3.5.5 so no issues here.
When I run npm i --save-dev webpack I get a babel-core error reading the following; it will not let me proceed without usinf webpack 1, 2 pr 2.1.0-beta
I cannot get past this and have search stackoverflow and multiple sites.
In my situation, I'm using it with Redux on Windows.
This is my error.
`-- UNMET PEER DEPENDENCY webpack#3.5.5
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.0.0 (node_modules\ch
okidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#
1.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}
)
npm WARN babel-loader#6.2.10 requires a peer of webpack#1 || 2 || ^2.1.0-beta ||
^2.2.0-rc but none was installed.
npm WARN prj400r#1.0.0 No description
npm WARN prj400r#1.0.0 No repository field.
Highlighting the babel-core error as being the most problematic. Any workaround?
Update babel-loader to version 7.x.x and it should solve your problem. The previous versions required webpack 1 and this support was dropped in version 7
Release v7.0.0