I try to add a search command for my bot, so I try to add the google extension with
npm i google
And I get :
npm WARN BAstLor#1.0.0 No description
npm WARN BAstLor#1.0.0 No repository field.
npm WARN BAstLor#1.0.0 No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.11 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
+ google#2.1.0
updated 1 package and audited 2557 packages in 8.968s
1 package is looking for funding
run `npm fund` for details
found 11 vulnerabilities (1 low, 7 moderate, 2 high, 1 critical)
run `npm audit fix` to fix them, or `npm audit` for details
EDIT : I tried to continue my code, and tried to do other npm install, and I have the same errors with same vulnerabilities
EDIT2 : No more problem, thanks
Related
I have a nodejs project docker build that was building just fine on Azure Pipeline. But about 10 days ago, the build output changed to have one additional line that I do not understand the cause of it. Its the line "+ xlsx#0.17.0" at the bottom (in bold in output below).
Nothing has changed in the code between when the output didn't have that additional line and now.
Nothing was changed in the docker file or build definition as well. In the package.json, I am referencing "xlsx: ^0.14.5". Even if I change that to just "xlsx: 0.14.5" the output log will contain "+ xlsx#0.17.0" which confuses me. Shouldn't it try to install exactly that version?
NOTE: The reason I ask is because when this docker image gets pushed to Amazon ECS, it throws "Module not found 'xlsx'" Error.
THank you for your help!
found 10 vulnerabilities (2 low, 4 moderate, 4 high)
run `npm audit fix` to fix them, or `npm audit` for details
> nodemon#1.19.4 postinstall /srv/node_modules/nodemon
> node bin/postinstall || exit 0
Love nodemon? You can now support the project via the open collective:
> https://opencollective.com/nodemon/donate
npm WARN pg-cursor#2.7.1 requires a peer of pg#^8 but none is installed. You must install peer dependencies yourself.
npm WARN swagger-ui-express#4.1.6 requires a peer of express#>=4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#2.3.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 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":"linux","arch":"x64"})
***+ xlsx#0.17.0***
added 663 packages from 361 contributors and updated 2 packages in 11.462s
39 packages are looking for funding
run `npm fund` for details
fixed 1 of 10 vulnerabilities in 1394 scanned packages
4 vulnerabilities required manual review and could not be updated
4 package updates for 5 vulnerabilities involved breaking changes
(use `npm audit fix --force` to install breaking changes; or refer to `npm audit` for steps to fix these manually)
Removing intermediate container 4c02dbafa75c
---> c010404a92cb
Step 9/30 : ADD . .
---> d1925852f28b
I can't comment so I will ask here:
Are you adding the package-lock.json file to the docker image? You're probably not, that's why npm is installing a newer version of the package.
That may fix the error if it's currently working on your dev environment. If not, how are you importing the package?
after i use npm install sass in cmd
then cmd show these errors
npm WARN saveError ENOENT: no such file or directory, open 'C:\Users\me\package.json'
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.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\me\package.json'
npm WARN me No description
npm WARN me No repository field.
npm WARN me No README data
npm WARN me No license field.
+ sass#1.32.8
added 15 packages from 18 contributors and audited 16 packages in 3.402s
1 package is looking for funding
run `npm fund` for details
found 0 vulnerabilities
i dont know how to solve these errors
Those are just npm warnings about the package you are installing, in your case you don't have to worry about them unless something is not working. You can ignore them if you like by running:
npm install sass --silent
npm docs
I got below error while I try to run npm install.
type:
npm install
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.9 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
audited 17160 packages in 10.766s
found 2 moderate severity vulnerabilities
run `npm audit fix` to fix them, or `npm audit` for details
It is not an error, it is just a warning. The warning indicates you are using Windows OS where the package has been designed for MacOS.
Unsupported platform for fsevents#1.2.9: wanted {"os":"darwin","arch":"any"}(current: {"os":"win32","arch":"x64"})
You can skip this warning and go forward. It will not effect in any ways in your development.
When I run npm audit fix it says fixed 0 of 2 vulnerabilities in 11294 scanned packages 2 vulnerabilities required manual review and could not be updated. Please provide any suggestion to resolve the this issue.
C:\Users\saivenkateswar.k\Pictures\botium-sample-eclipse-master\botium-sample-eclipse-master>npm audit fix
npm WARN botium-sample-watson#2.0.0 No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.7 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) up to date in 35.383s
fixed 0 of 2 vulnerabilities in 11294 scanned packages
2 vulnerabilities required manual review and could not be updated
C:\Users\saivenkateswar.k\Pictures\botium-sample-eclipse-master\botium-sample-eclipse-master>npm audit
=== npm audit security report ===
Manual Review
Some vulnerabilities require your attention to resolve
Visit https://go.npm.me/audit-guide for additional guidance
Moderate Sandbox Breakout / Arbitrary Code Execution
Package static-eval
Patched in No patch available
Dependency of botium-bindings [dev]
Path botium-bindings > botium-core > jsonpath > static-eval
More info https://nodesecurity.io/advisories/758
Moderate Sandbox Breakout / Arbitrary Code Execution
Package static-eval
Patched in No patch available
Dependency of botium-cli [dev]
Path botium-cli > botium-core > jsonpath > static-eval
More info https://nodesecurity.io/advisories/758
found 2 moderate severity vulnerabilities in 11294 scanned packages
2 vulnerabilities require manual review. See the full report for deta
I have installed Latest nodeJS(v.8.9.1) and npm(6.1.0), though im getting below problem
npm WARN saveError ENOENT: no such file or directory, open
'F:\AngularProject\Node\package.json'
npm notice created a lockfile as package-lock.json. You should commit this
file.
npm WARN enoent ENOENT: no such file or directory, open
'F:\AngularProject\Node\package.json'
npm WARN #angular/core#2.4.10 requires a peer of rxjs#^5.0.1 but none is
installed. You must install peer
dependencies yourself.
npm WARN Node No description
npm WARN Node No repository field.
npm WARN Node No README data
npm WARN Node No license field.
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":"darw
in","arch":"any"} (current: {"os":"win32","arch":"x64"})
+ angular-cli#1.0.0-beta.28.3
added 922 packages from 761 contributors and audited 5006 packages in
280.149s
found 14 vulnerabilities (1 low, 9 moderate, 4 high)
run `npm audit fix` to fix them, or `npm audit` for details
I have searched in net,but couldn't sort out.I tried the some possible ways like clear npm cache,installed latest npm,Tried in administrator console. But still unable to find out.