could not find a module after add new package in docker [duplicate] - node.js

I am trying to install react-html-parser in my docker container 'client':
docker-compose.yml
client/
Dockerfile-dev
node_modules/
src/
components/
Seeds.jsx
and try and import it here:
Seeds.jsx
import React, { Component } from 'react';
import ReactHtmlParser, { processNodes, convertNodeToElement, htmlparser2 }
from 'react-html-parser';
import axios from 'axios';
'axios' and 'react' are instaled allright, but not 'react-html-parser'. Console logs me the error:
index.js:1437 ./src/components/Seeds.jsx
Module not found: Can't resolve 'react-html-parser' in '/usr/src/app/src/components'
package.json
{
"name": "client",
"version": "0.1.0",
"private": true,
"dependencies": {
"axios": "^0.18.0",
"react": "^16.8.2",
"react-dom": "^16.8.2",
"react-router-dom": "^4.3.1",
"react-scripts": "2.1.5",
"react-html-parser":"^2.0.2", # <---------NEW
"spotify-web-api-js": "^0.22.1"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
},
"eslintConfig": {
"extends": "react-app"
},
"browserslist": [
">0.2%",
"not dead",
"not ie <= 11",
"not op_mini all"
],
"devDependencies": {
"enzyme": "^3.8.0",
"enzyme-adapter-react-16": "^1.7.1"
}
}
Dockerfile-dev
# base image
FROM node:11.6.0-alpine
# set working directory
WORKDIR /usr/src/app
# add `/usr/src/app/node_modules/.bin` to $PATH
ENV PATH /usr/src/app/node_modules/.bin:$PATH
# install and cache app dependencies
COPY package.json /usr/src/app/package.json
RUN npm install --silent
RUN npm install react-scripts#2.1.2 -g --silent
# start app
CMD ["npm", "start"]
docker-compose.yml
client:
build:
context: ./services/client
dockerfile: Dockerfile-dev
volumes:
- './services/client:/usr/src/app'
- '/usr/src/app/node_modules'
ports:
- 3000:3000
environment:
- NODE_ENV=development
- REACT_APP_WEB_SERVICE_URL=${REACT_APP_WEB_SERVICE_URL}
depends_on:
- web
I can'f find the module inside my node_modules folder...
what am I missing here?
EDIT: npm install without --silent:
npm WARN deprecated fsevents#1.2.4: Way too old
npm WARN deprecated core-js#2.6.4: core-js#<2.6.8 is no longer maintained. Please, upgrade to core-js#3 or at least to actual version of core-js#2.
npm WARN deprecated joi#11.4.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated circular-json#0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated kleur#2.0.2: Please upgrade to kleur#3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit <https://github.com/lukeed/kleur/releases/tag/v3.0.0\> for migration path(s).
npm WARN deprecated flatten#1.0.2: I wrote this module a very long time ago; you should use something else.
npm WARN deprecated hoek#4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated topo#2.0.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated left-pad#1.3.0: use String.prototype.padStart()
> core-js#2.6.9 postinstall /usr/src/app/node_modules/core-js
> node scripts/postinstall || echo "ignore"
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 -)
> core-js-pure#3.1.3 postinstall /usr/src/app/node_modules/core-js-pure
> node scripts/postinstall || echo "ignore"
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 -)
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN ts-pnp#1.1.2 requires a peer of typescript#* 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":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.9 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

When your docker-compose.yml file says:
volumes:
- '/usr/src/app/node_modules'
You're telling Docker your node_modules directory contains critical data that needs to be persisted across container runs. The first time you launch the container it will get populated from the image, but because that directory contains critical data, Docker will never ever update it again, even if you try to npm install additional modules.
For a near-term workaround, it's enough to docker-compose stop; docker-compose rm; docker-compose up --build your containers. Deleting the existing container (and its anonymous volume) is important.

Try this command npm i react-html-parser --force

Related

Creating react app with npx, npm install returns warnings

I just started making my first react/firebase app and ran the command npx create-react-app test-app. Once I cd into my folder I ran npm i --save firebase. However, this created '10 high severity vulnerabilities'. I ran npm audit fix --force as it suggested to me, but surprisingly that threw a lot of deprication warnings and gave more vulnerabilities.
npm WARN using --force Recommended protections disabled.
npm WARN audit Updating react-scripts to 4.0.3, which is a SemVer major change.
npm WARN deprecated #npmcli/move-file#1.1.2: This functionality has been moved to #npmcli/fs
npm WARN deprecated source-map-url#0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated flatten#1.0.3: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated #hapi/topo#3.1.6: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated #hapi/bourne#1.3.2: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated rollup-plugin-terser#5.3.1: This package has been deprecated and is no longer maintained. Please use #rollup/plugin-terser
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 source-map-resolve#0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated querystring#0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated sane#4.1.0: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
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 chokidar#2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated chokidar#2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer 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 querystring#0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated babel-eslint#10.1.0: babel-eslint is now #babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated #hapi/address#2.1.4: Moved to 'npm install #sideway/address'
npm WARN deprecated rollup-plugin-babel#4.4.0: This package has been deprecated and is no longer maintained. Please use #rollup/plugin-babel.
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated #hapi/hoek#8.5.1: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated #hapi/joi#15.1.1: Switch to 'npm install joi'
npm WARN deprecated 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 cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
I'm out of ideas how to fix this. I managed to find this earlier post. But after attempting those answers, I did not get any different result.
package.json
{
"name": "test-app",
"version": "0.1.0",
"private": true,
"dependencies": {
"#testing-library/jest-dom": "^5.16.5",
"#testing-library/react": "^13.4.0",
"#testing-library/user-event": "^13.5.0",
"firebase": "^9.15.0",
"react": "^18.2.0",
"react-dom": "^18.2.0",
"react-scripts": "^4.0.3",
"web-vitals": "^2.1.4"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
},
"eslintConfig": {
"extends": [
"react-app",
"react-app/jest"
]
},
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
}
}
I did nothing to the files itselfs, just those 3 command lines I showed at the top.

How to resolve an error with npm run serve

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

npm install command does not work with Laravel version 5.8

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

npm install giving Error after so many WARN

My ReactJS project was working all fine till last week but from Sunday its giving below error on npm install:
PS C:\Projects\Interface\ClientApp> npm install
npm WARN deprecated material-ui-icons#1.0.0-beta.36: Use #material-ui/icons instead
npm WARN deprecated material-ui#0.20.2: You can now upgrade to #material-ui/core
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 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 material-ui-pickers#2.2.4: You can now upgrade to
#material-ui/pickers. Documentation for v2 can be found at
https://material-ui-pickers-v2.dmtr-kovalenko.now.sh/
npm WARN deprecated extract-text-webpack-plugin#3.0.2: Deprecated. Please use
https://github.com/webpack-contrib/mini-css-extract-plugin
npm WARN deprecated fsevents#1.1.2: fsevents 1 will break on node v14+ and could
be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated core-js#1.2.7: 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 WARN deprecated left-pad#1.3.0: use String.prototype.padStart()
npm WARN deprecated browserslist#2.11.3: Browserslist 2 could fail on reading
Browserslist >3.0 config used in other tools.
npm WARN deprecated sw-precache#5.2.1: Please migrate to Workbox:
https://developers.google.com/web/tools/workbox/guides/migrations/migrate-from-sw
npm WARN deprecated chokidar#1.7.0: Chokidar 2 will break on node v14+.
Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated sw-toolbox#3.6.0: Please migrate to Workbox:
https://developers.google.com/web/tools/workbox/guides/migrations/migrate-from-sw
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 hawk#3.1.3: This module moved to #hapi/hawk. Please make sure to
switch over as this distribution is no longer supported and may contain
bugs and critical security issues.
npm WARN deprecated request#2.81.0: 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 request#2.88.2: request has been deprecated, see
https://github.com/request/request/issues/3142
npm WARN deprecated os-homedir#2.0.0: This is not needed anymore.
Use `require('os').homedir()` instead.
npm WARN deprecated browserslist#1.7.7: Browserslist 2 could fail on reading
Browserslist >3.0 config used in other tools.
npm WARN deprecated circular-json#0.3.3: CircularJSON is in maintenance only,
flatted is its successor. npm WARN deprecated hoek#2.16.3: This version
has been deprecated in accordance with the hapi support policy (hapi.im/support).
Please upgrade to the latest version to get the best features, bug fixes,
and security patches. If you are unable to upgrade at this time, paid
support is available for older versions (hapi.im/commercial).
npm WARN deprecated cryptiles#2.0.5: This version has been deprecated in accordance
with the hapi support policy (hapi.im/support). Please upgrade to the
latest version to get the best features, bug fixes, and security patches.
If you are unable to upgrade at this time, paid support is available for
older versions (hapi.im/commercial).
npm WARN deprecated boom#2.10.1: This version has been deprecated in accordance
with the hapi support policy (hapi.im/support). Please upgrade to the
latest version to get the best features, bug fixes, and security patches.
If you are unable to upgrade at this time, paid support is available for
older versions (hapi.im/commercial).
npm WARN deprecated sntp#1.0.9: This module moved to #hapi/sntp. Please make sure
to switch over as this distribution is no longer supported and may contain
bugs and critical security issues.
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 ERR! Unexpected end of JSON input while parsing near '...on" : "10.16.3"
npm ERR! }'
npm ERR! A complete log of this run can be found in: npm ERR!
C:\Users\AppData\Roaming\npm-cache\_logs\2020-07-06T10_18_35_852Z-debug.log
Note
I have upgraded the npm from 6.9.0 to 6.14.5 then also facing same issue
I have removed package.json.lock and node_modules then also facing same issue
Please do let me know what else I am missing ?
--------------My package.json--------------
{
"name": "clientapp",
"version": "0.1.0",
"private": true,
"dependencies": {
"#material-ui/core": "^4.9.5",
"#material-ui/icons": "^4.4.1",
"#material-ui/lab": "^4.0.0-alpha.45",
"#material/typography": "^3.1.0",
"#trendmicro/react-sidenav": "^0.4.5",
"axios": "^0.19.0",
"bootstrap": "^3.4.1",
"flux": "^3.1.3",
"jquery": "^3.4.1",
"match-sorter": "^4.0.2",
"material-grid": "^0.1.0",
"material-table": "^1.54.2",
"material-ui": "^0.20.2",
"material-ui-colors": "^1.0.0",
"material-ui-icons": "^1.0.0-beta.36",
"mdbreact": "^4.22.0",
"oidc-client": "^1.5.4",
"plotly.js": "^1.49.4",
"prop-types": "^15.7.2",
"react": "^16.13.0",
"react-bootstrap": "^0.31.5",
"react-bootstrap-tabs": "^1.0.2",
"react-dom": "^16.13.0",
"react-flippy": "^0.1.5",
"react-loader-spinner": "^3.1.5",
"react-minimal-pie-chart": "^6.0.1",
"react-plotly.js": "^2.3.0",
"react-redux": "^7.1.3",
"react-redux-loading-bar": "^4.5.0",
"react-router-bootstrap": "^0.24.4",
"react-router-dom": "^4.2.2",
"react-scripts": "1.0.17",
"react-slideshow-image": "^1.4.0",
"react-sortable-tree": "^2.7.1",
"react-stack-grid": "^0.7.1",
"react-stonecutter": "^0.3.10",
"react-table": "^7.0.0-rc.15",
"react-web-tabs": "^1.0.1",
"redux": "^4.0.4",
"rimraf": "^2.6.2",
"webpack": "*"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
}
}
If you see the log, for old packages, it gives a Warning and not an Error. The error is actually this line: npm ERR! Unexpected end of JSON input while parsing near '...on" : "10.16.3"
npm ERR!}'
Since you have not included the entire log, with this, I can guess it is possibly an ambiguity issue due to references not properly resolved!
Open command prompt/powershell/terminal, etc. with admin privilege. Do as below: -
sudo npm cache clean --force
sudo npm cache verify
Delete the package-lock.json file located in C:\Users\<your_username>
Try installing your project dependencies now from your project folder with npm i.
Note: - If this doesn't work, follow the same process as above (again) and uninstall the npm and node and reinstall it. It should work then!
Try upgrading to #material-ui/core.
material-ui package is deprecated.

NPM install Gulp/Elixir

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.

Resources