All node, globally installed npm commands stopped working.
They do not work when I re-install locally either.
node server.js works, but crashed because my mongod command does not work.
I think I screwed up my enviro PATH variables.
Can a PC user take a screenshot of their enviro variables (or just post the relavant one) so I can try to re-create it?
When i try to re-install I get this error:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.0.0 (node_modules\nodemon\node_modules\chokidar\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"})
I had a similar problem with webpack not working and we were able to spot an irregularity in the path, which happened to be on my desktop and I cleaned up my desktop and problem solved. Can anyone see anything irregular about the path in the first warning> Or just know how to get my commands working again?
Related
I am trying to install sociobaord
from the following URL
https://github.com/socioboard/Socioboard-4.0
I tried installing a part of it i.e https://github.com/socioboard/Socioboard-4.0/tree/master/socioboard-web-php and have succeeded
but
I am unable to install the API part https://github.com/socioboard/Socioboard-4.0/tree/master/socioboard-api
when I am trying to install Socioboard API I am getting following errors
D:\wamp\www\social\user>npm install
npm WARN user#1.0.0 No description
npm WARN user#1.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"})
audited 877396 packages in 46.139s
found 0 vulnerabilities
and
D:\wamp\www\social\library\sequelize-cli> ../node_modules/.bin/sequelize db:migrate
'..' is not recognized as an internal or external command,
operable program or batch file.
After going through the issue with you .. we came to figure that you need to install all the packages in all the folders as per the documentation.
Also, their documentation is missing that to install the app correctly we need to install sequelize-cli, and preferably to install it globally.
once installed .. just remove the full link to the sequelize binary ../node_modules/.bin/sequelize and type sequelize instead
I'm trying to install Angular using the Angular CLI but I'm getting an error when I try to run this command.
Command
npm install -g #angular/cli
Error:
C:\Users\abc>npm install -g #angular/cli
C:\Users\abc\AppData\Roaming\npm\ng -> C:\Users\abc\AppData\Roaming\npm\node_modules\#angular\cli\bin\ng
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.7 (node_modules\#angular\cli\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"})
+ #angular/cli#7.3.6
updated 1 package in 102.686s
Node Version v10.15.3
This is a warning not an error, and it's because you're on Windows. FSevents only works on Mac so it's not needed on Windows and that's why it's SKIPPING OPTIONAL DEPENDENCY.
And no as of right now there is no way to get rid of that being printed into the console so just ignore it given the fact that it's not doing anything anyways rather it's just being a bit verbose and telling you that it's not being used.
This is because you're running on windows. A lot of apps use that library, but it only works on the Mac, so they use something else for Windows and Linux. That's why it's listed as "optional". You can ignore the warning.
I received an app that uses quorra, so I installed quorra via the instructions on the webpage
λ npm install -g quorra-cli
C:\Users\****\AppData\Roaming\npm\quorra -> C:\Users\****\AppData\Roaming\npm\node_modules\quorra-cli\quorra.js
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.4 (node_modules\quorra-cli\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"})
+ quorra-cli#1.0.0
added 209 packages from 124 contributors in 18.942s
But then when I try to run anything, like
quorra ride
quorra new
quorra -v
I get:
'quorra' is not recognized as an internal or external command,
operable program or batch file.
It seems like it cant find where to run the quorra command, but I installed it so I dont understand what else I am supposed to do I didnt find anything else on the docs.
I even tried adding the quora folder
C:\Users****\AppData\Roaming\npm\node_modules\quorra-cli
into my path variable but no luck
Any help?
I hate warnings.
Especially when those warnings are completely ignorable.
Most warnings I encounter are non-clean code warnings and I like to have my code clean. Other warning are actual errors.
Sometimes I miss error warnings because they were "hidden" between other warnings.
So I like to keep things clean.
Thus when I do npm install and see this:
[folatt#MyComputer ~]$ npm install
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"})
up to date in 33.232s
I want to get rid of that warning.
I know of the --no-optional argument, but that seems hacky to me as well.
Isn't there anything one can do in package.json to get rid of this warning?
This has been fixed in npm v7. If you update your npm, you shouldn't see these unactionable warnings anymore.
On this GitHub question, someone confirmed that the fsevents skipping optional dependency warnings have been removed in npm v7:
Yep, it’s fixed in v7.
(source)
You should be able to silence those messages with environment values.
npm_config_loglevel=silent
Default: “notice”
Values: “silent”, “error”, “warn”, “notice”, “http”,
“timing”, “info”, “verbose”, “silly”
Details here;
https://docs.npmjs.com/misc/config#loglevel
You can use npm audit fix command.
Also if you could share your package.json file that will be helpful
I'm trying to run this project.
After updating minimatch version to 3.10.9, I'm getting the following error:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.0.0 (node_modules\webpack\node_modules\watchpack\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.0.14: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})
My configuration:
Node v - 4.4.2
npm v - 3.10.9
32 bit windows OS
It's a warning, not an error. It occurs because fsevents is an optional dependency, used only when project is run on macOS environment (the package provides 'Native Access to Mac OS-X FSEvents').
And since you're running your project on Windows, fsevents is skipped as irrelevant.
There is a PR to fix this behaviour here: https://github.com/npm/cli/pull/169
This still appears to be an issue, causing package installations to be aborted with warnings about optional packages not being installed because of "Unsupported platform".
The problem relates to the "shrinkwrap" or package-lock.json which gets persisted after every package manager execution. Subsequent attempts keep failing as this file is referenced instead of package.json.
Adding these options to the npm install command should allow packages to install again.
--no-optional argument will prevent optional dependencies from being installed.
--no-shrinkwrap argument, which will ignore an available package lock or
shrinkwrap file and use the package.json instead.
--no-package-lock argument will prevent npm from creating a package-lock.json file.
The complete command looks like this:
npm install --no-optional --no-shrinkwrap --no-package-lock
nJoy!
Using parameter --force:
npm i -f
This answer worked for me, add this to your package.json
"optionalDependencies": {
"fsevents": "^2.3.2"
}
Unsupported platform for fsevents
The current best solution is upgrading your version of npm, which won't have this warning.
If using a Windows machine, an easy way to upgrade is with the tool Upgrade npm on Windows.