Couldn't install optional dependency: Unsupported #9204
Comments
|
I'm switching to |
|
I also have some "Unsupported" option dependency error: What does it mean? |
|
Same here.
|
|
Same here. and then getting: My package.json: {
"name": "Sodruzhestvo",
"version": "2.0.0",
"browser": {},
"browserify": {
"transform": [
"envify",
"brfs"
]
},
"devDependencies": {
"brfs": "",
"browser-sync": "",
"browserify": "",
"envify": "",
"exorcist": "",
"gulp": "",
"gulp-autoprefixer": "",
"gulp-changed": "",
"gulp-concat": "",
"gulp-data": "",
"gulp-debug": "",
"gulp-if": "",
"gulp-imagemin": "",
"gulp-jade": "",
"gulp-minify-css": "",
"gulp-minify-html": "",
"gulp-notify": "",
"gulp-rename": "",
"gulp-sass": "",
"gulp-sourcemaps": "",
"gulp-streamify": "",
"gulp-ng-html2js": "",
"gulp-tap": "",
"gulp-uglify": "",
"gulp-util": "",
"gulp-cat": "",
"pretty-hrtime": "",
"js-yaml": "",
"merge-stream": "",
"require-dir": "",
"vinyl-source-stream": "",
"watchify": "",
"yargs": ""
},
"dependencies": {
"moment": "^2.10.6"
}
}
|
|
What version of NPM are you guys running? I'm having the same issue on version |
|
@drmyersii 3.3.4 Windows 10 |
|
same problem, 3.3.3 on Ubuntu |
|
same problem ubuntu, when testing it seems this also occurs with 3.2, so I'm using |
|
same problem, windows 8 version 3.3.3 |
|
Same issue. Linux Mint 17.2, Node.js 4.1.1, npm 3.3.3 P/S: remove entirely node_modules folder and then run "npm install", it works as well. |
|
+1, 3.3.3 on Win7x64, running npm over maven, all my dependencies: |
|
I think we have enough +1 now to validate this issue. Please use the Subscribe button instead of adding another +1 from now on. 👍 Current workaround is to completely remove the |
|
@rafaelmagu, which is not a workaround for my case at all. |
|
If that doesn't work, reverting to |
|
workaround does not work for me either - can this be regressed soon? thanks |
|
I deleted the folder and done npm install again and still whines about it. However it doesn't stop the process so there wouldn't be a need for downgrading to npm@2, would it? |
|
Same problem, Ubuntu 14.04, NPM 3.3.4. |
|
I have the same issue on one of my servers (Ubuntu), removing the node_modules doesn't fix the problem Everything works fine if I revert back to Npm 2.x.x |
|
Same here, in arch linux and everything works fine too for me only if I revert back to Npm 2.x.x |
|
Not fixed in 3.3.5 |
|
Still exists in 3.3.6 |
|
Folks with |
|
I have this issue as well with npm 3.3.8 and 3.3.9 on Windows 7 and Windows Server 2012. The "workaround" - deleting node_modules and executing npm install - does not work for me either. |
|
Hi, |
|
Hi , I am able to resolve my issue now after using below command:- $ npm install --no-bin-links since i had to further install bower, so i used: Then i wanted to build my wordpress sage template. I used 👎 $ npm rebuild node-sass <- gave again some symbolic link error, I choose below command which worked fine. $ npm rebuild node-sass --no-bin-links Further i was able to use gulp to build. Thanks. |
|
@replete - Are you getting an error when running your npm install or just the standard |
|
VS thinks the npm deps are unmet, so you see the warning in the solution It is always fsevents. On 7 Oct 2016 01:16, "Cole Chamberlain" notifications@github.com wrote:
|
|
@replete - If VS is throwing errors due to the |
|
@cchamberlain I believe it is probably npm:
Therefore, I believe this error is caused by the version of npm|Node shipped with Visual Studio 2015.3. I only comment here so that others in my predicament might find a workaround. |
|
@replete - Thanks for the additional information. Many windows bugs have been targeted between that old version and now, I think it would likely work if you could update the internal version. Until the version is updated to a current version, I would still qualify this a VS bug unless this is happening in the current published npm version. @felixrieseberg maybe knows something of this internally maintained npm? |
|
@cchamberlain No worries. I will wait for the Visual Studio web tools to be updated and continue using my workaround, as manual upgrading of the web tools could cause hard-to-diagnose problems should there be any breaking change between the versions. |
|
I to had this problem with Visual Studio 2015 and I found a post describing how to make VS not use its internal Node.js and NPM but your own install |
|
@Alam1386 - Your issue is unrelated to this optional dependencies issue and does not belong here. On a separate note, why are you trying to install bootstrap into itself? |
|
I have fixed the issue like this: Installed the latest version of npm: npm install -g npm@next |
|
Ending up getting the output below. Running on CentOS 7 x64 (doesn't happen on Mac) I have a git+ssh dependency in my package.json, in addition to others Have tried adding fsevents as an optional dependency, but it has not helped. I'm not sure where the issue falls, and I've opened one here also |
|
@replete Take a look at #14042 (comment), solved the issue for me in a different case. Same core problem though - fsevents was getting installed regardless of being optional. Key addendum though: the comment talks about downgrading to 3.10.7, but 3.10.10 and up fix the issue. Adding and running |
|
While install ionic using below command: npm install ionic -g npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\io any body help to resolve this issue Thanks |
|
still
|
|
npm install //why? npm-v 3.10.8 && 3.10.9&& 4.2 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents): 用git bash就会出现这种警告，并且退出 用cmd就可以好好使用 |
latest ubuntu |
|
@malikasinger1 That is not an error, that is just letting yoy know that fsevents isn't meant for you OS. |
|
Without any changes this has started happening - Please note that this is actually an ERR not a warning and breaks our builds.. I tried adding the --no-optional flag but that didn't help. |
|
Try running |
|
I'm seeing the same problem as Foxhoundn above: this is now an ERR. I've tried this with the new npm, both LTS and current (3.10.8). npm ls --only=prod fsevents just returns `-- (empty) NOTE: I fixed this problem temporarily by removing fsevents from our npm-shrinkwrap.json file. But the dependency in there is clearly marked as optional (and dev): "fsevents": { |
|
[pankaj.kulshrestha@www-test-01 SimpleWebRTC]$ sudo npm install
fs.js:641 Error: EACCES: permission denied, open '/var/www/html/pankaj/nodejs_proj/SimpleWebRTC/.git/hooks/pre-commit' npm ERR! git-validate@2.2.2 install: npm ERR! Please include the following file with any support request: |
|
I can confirm that using the I did NOT have to use this patch from @greyvugrin to get it working: |
|
|
|
Under most cases you shouldn't need to physically add Using CLI option |
and others
Hello. I've faced some issues, possibly it was caused by updating npm from v2 to v3 on my machine. I've tried to solve this by myself but had no success.
I'm using my homedir as a place for common-used npm-packages.
So, when I do
npm i fibonacciin~I get~/node_modules/fibonacci. This works even if I have no~/package.json(I recieve warning, but this is ok for me). I was using this for tests: any node script in my home subtree is able to access modules from~/node_modules. I also have my own packages in~/node_modulesas git-repositories, synchronized with my github repos. This works inv2, but inv3I got this error on every install:Here I'm trying to install
lodash; andrepl.jsis my own package, installed as git-repo. So, when I have any git repositories in~/node_modulesthey prevent me from installing any other ordinary package.How I'm trying to fix this:
Please, help me to overcome this issue.
The text was updated successfully, but these errors were encountered: