npm install error - No compatible version found: fs@0.0.2 #13743

dotannn · 2016-08-23T18:31:36Z

I'm opening this issue because:

Hi, I suddenly started to get weird errors after npm install, although didn't change anything

What's going wrong?

i get npm ERR! No compatible version found: fs@0.0.2

supporting information:

npm WARN deprecated tough-cookie@2.2.2: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated cross-spawn-async@2.2.4: cross-spawn no longer requires a build toolchain, use it instead!
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.14
npm ERR! Linux 3.19.0-47-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v6.2.2
npm ERR! npm v3.9.5

npm ERR! No compatible version found: fs@0.0.2
npm ERR! Valid install targets:
npm ERR! 0.0.1-security
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request:
npm ERR! /home/dotan/work/code/personify/orderingbot/npm-debug.log

adamchenwei · 2016-08-23T18:42:48Z

samething here!

part of the log

358730 info postinstall node-sass@3.8.0
358731 verbose unsafe-perm in lifecycle true
358732 verbose unlock done using /home/vagrant/.npm/_locks/node-sass-9894a549776d5f33.lock for /home/vagrant/web/app/node_modules/gulp-sass/node_modules/node-sass
358733 verbose about to build /home/vagrant/web/app/node_modules/gulp-sass
358734 info build /home/vagrant/web/app/node_modules/gulp-sass
358735 info install gulp-sass@2.3.2
358736 info postinstall gulp-sass@2.3.2
358737 verbose unlock done using /home/vagrant/.npm/_locks/gulp-sass-6091a8f93f433587.lock for /home/vagrant/web/app/node_modules/gulp-sass
358738 verbose stack Error: version not found: fs@0.0.2
358738 verbose stack     at setData (/usr/lib/node_modules/npm/lib/cache/add-named.js:137:12)
358738 verbose stack     at RES (/usr/lib/node_modules/npm/node_modules/inflight/inflight.js:23:14)
358738 verbose stack     at f (/usr/lib/node_modules/npm/node_modules/once/once.js:17:25)
358738 verbose stack     at fixName (/usr/lib/node_modules/npm/lib/cache/add-named.js:29:5)
358738 verbose stack     at saved (/usr/lib/node_modules/npm/lib/cache/caching-client.js:173:7)
358738 verbose stack     at /usr/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:210:7
358738 verbose stack     at FSReqWrap.oncomplete (fs.js:95:15)
358739 verbose statusCode 404
358740 verbose cwd /home/vagrant/web/app
358741 error Linux 3.10.0-327.22.2.el7.x86_64
358742 error argv "/usr/bin/node" "/usr/bin/npm" "install" "--no-bin-links"
358743 error node v0.12.9
358744 error npm  v2.14.9
358745 error version not found: fs@0.0.2
358746 error If you need help, you may report this error at:
358746 error     <https://github.com/npm/npm/issues>

jfortier-haptiq · 2016-08-23T18:44:34Z

+1 here

Going to:
https://registry.npmjs.org/fs

Reveals some security messages such as: "This package name is not currently in use, but was formerly occupied by another package. To avoid malicious use, npm is hanging on to the package name, but loosely, and we'll probably give it to you if you want it."

So to me it sounds like a 404, but because it was previously registered they're not allowing another package to take it's place. I tried widening the version scope in package.json file to see if maybe it was just deprecated for a newer version. None that I can see.

dotannn · 2016-08-23T18:53:32Z

I found that there are two packages in my dependencies who provoke this error :

npm (i don't know why but I had it in my dependencies)
1. paycryptor https://github.com/richardgirges/paycryptor

srikiraju · 2016-08-23T19:03:12Z

+1 here

2865 silly fetchPackageMetaData Error: No compatible version found: fs@0.0.2
2865 silly fetchPackageMetaData Valid install targets:
2865 silly fetchPackageMetaData 0.0.1-security
2865 silly fetchPackageMetaData
2865 silly fetchPackageMetaData     at pickVersionFromRegistryDocument (/Code/web-ux/env/lib/node_modules/npm/lib/fetch-package-metadata.js:170:16)
2865 silly fetchPackageMetaData     at /Code/web-ux/env/lib/node_modules/npm/node_modules/iferr/index.js:13:50
2865 silly fetchPackageMetaData     at /Code/web-ux/env/lib/node_modules/npm/lib/utils/pulse-till-done.js:19:8
2865 silly fetchPackageMetaData     at saved (/Code/web-ux/env/lib/node_modules/npm/lib/cache/caching-client.js:174:7)
2865 silly fetchPackageMetaData     at /Code/web-ux/env/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:210:7
2865 silly fetchPackageMetaData     at FSReqWrap.oncomplete (fs.js:82:15)
2865 silly fetchPackageMetaData  error for fs@0.0.2 [Error: No compatible version found: fs@0.0.2
2865 silly fetchPackageMetaData Valid install targets:
2865 silly fetchPackageMetaData 0.0.1-security
2865 silly fetchPackageMetaData ]

adamchenwei · 2016-08-23T19:04:15Z

How to bring important ticket to attention to the npm admin???

jfortier-haptiq · 2016-08-23T19:08:30Z

Apparently the 'fs' package is now part of the npm core, and is no longer required for import. I simply removed the package from my package.json file, did another npm installand was able to build using gulp with no issues. Just sucks for those of us that maintain slightly dated products. http://stackoverflow.com/questions/24594796/node-js-npm-install-fs-error

Edit: Why all the down vote?

Edit 2: Sorry people who have dependencies inside their own package.json files. Track them down with npm ls. No reason to down vote though IMO.

Apparently the 'fs' package is now part of the npm core, and is no longer required for import. npm/npm#13743 (comment)

srikiraju · 2016-08-23T19:20:45Z

How can we determine which of the dependencies has fs as it's dependency?
npm ls only shows the dep-graph for stuff that's installed.

VictorSage · 2016-08-23T19:22:35Z

My package does not directly reference fs package. How do we know which one create this dependency?

prashanthparsi · 2016-08-23T19:24:07Z

Happening for me as well. Any solutions or thoughts?

DVLP · 2016-08-23T19:30:07Z

Same problem,
I downgraded to 0.0.1-security to see if this will help

adamchenwei · 2016-08-23T19:30:45Z

Wait, for node apps that use earlier version like 0.12.9, what should we do

codingmaven · 2016-08-23T19:32:48Z

Same issue here

prashanthparsi · 2016-08-23T19:33:38Z

I had the fs dependency listed in package.json. I removed it and npm install is running now.

rameshthoomu · 2016-08-23T19:34:43Z

same issue here.. What to do..

adamchenwei · 2016-08-23T19:38:51Z

One of our dependencies has dependencies, that includes "fs": "0.0.2",. I think that is the issue for us.

chrisbolin · 2016-08-23T19:40:04Z

If you don't depend on it directly, you can use npm ls to find which of your dependencies depends on fs. If you are super lucky, you might have control over that dependency.

VictorSage · 2016-08-23T19:40:09Z

remove the line make npm install works. There should be other solutions.

see npm/npm#13743

srikiraju · 2016-08-23T19:44:51Z

@chrisbolin My npm ls does not list fs@0.0.2, yet npm install tries to install it. I believe npm ls only lists packages that are currently installed

DVLP · 2016-08-23T19:45:32Z

To fix the problem delete this line

"fs": "0.0.2",
from your package.json

Beginners(like my team over a year ago) put this dependency in their code but it's a built-in so there's no need to install this.

quantizor · 2016-08-23T19:46:56Z

It's a built-in, don't know why people are putting that in their dependencies...

robwalch · 2016-08-23T19:50:45Z

Found the dep, but still wondering why this was ignored by the registry until recently...

zkat · 2016-08-23T19:52:34Z

Hey y'all -- this is not really an official response cause I still gotta talk to folks, but hang in there: you don't need fs at all, because it's built-in with Node, and installing the fs package was not doing anything for you. It is entirely safe (and recommended) that you remove this dependency.

For those of you with transitive dependencies asking for this package, stand by for that to get fixed, and a more official explanation of what's up. :)

adamchenwei · 2016-08-23T19:56:54Z

@zkat is fs default dep for node version 0.12.9 that not required to import?

zkat · 2016-08-23T19:58:47Z

@adamchenwei It has been a native node module since forever, afaik, and you literally never needed to npm install fs, for any version of node.

seldo · 2016-08-23T20:37:21Z

TLDR: Human error, specifically this human. I approved unpublishing it instead of deprecating it because I didn't properly check the deps count.

as per npm/npm#13743

jokeyrhyme · 2016-08-24T02:52:52Z

I highly recommend checking the names of modules that are built-in to Node.js:

https://github.com/nodejs/node/tree/master/lib

You should NOT be using npm or package.json to install any packages that have the same names as the built-in modules.

YurySolovyov · 2016-08-24T09:04:38Z

I just went ahead and created issues for the first page of npm search for dependencies of fs, but doing it manually is hard.
I encourage everyone to go ahead and reach to the rest of module authors and get this fixed.
Snippet I used

# title
No need to use fs as npm dependency

# body
Hi!
`fs` is a node core module, there is no need to include it as npm dependency
See https://github.com/npm/npm/issues/13743

* Removing fs dependency + Bumping up version Apparently the 'fs' package is now part of the npm core, and is no longer required for import. npm/npm#13743 (comment)

leog added a commit to leog/git-pre-commit that referenced this issue Aug 23, 2016

Removing fs dependency

2b96d93

Apparently the 'fs' package is now part of the npm core, and is no longer required for import. npm/npm#13743 (comment)

leog mentioned this issue Aug 23, 2016

Removing fs dependency as it is part of Node.js core kazazor/git-pre-commit#22

Merged

VictorSage mentioned this issue Aug 23, 2016

remove fs package Sage/carbon-factory#82

Merged

zkat added the support label Aug 23, 2016

NiklasMerz added a commit to NiklasMerz/ng-cordova that referenced this issue Aug 23, 2016

Removed invalid fs dependencies

2eb8b01

see npm/npm#13743

chrisbolin mentioned this issue Aug 23, 2016

remove fs dependency FormidableLabs/ecology#47

Merged

zkat closed this as completed Aug 23, 2016

zkat added the registry label Aug 23, 2016

kanaabe mentioned this issue Aug 23, 2016

@craigspaeth Add Yoast artsy/positron#796

Merged

jonfreedman added a commit to symphonyoss/hubot-symphony that referenced this issue Aug 23, 2016

fix: remove fs dependency

4801ca6

as per npm/npm#13743

hermansb mentioned this issue Oct 12, 2016

Remove 'fs' dependency IBM/node-log4js-qradar-syslog-appender#6

Merged

mikaoelitiana mentioned this issue Jun 13, 2017

ERR! notarget 0.0.1-security mikaoelitiana/cordova-ios-plugin-no-export-compliance#5

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

npm install error - No compatible version found: fs@0.0.2 #13743

npm install error - No compatible version found: fs@0.0.2 #13743

dotannn commented Aug 23, 2016

adamchenwei commented Aug 23, 2016 •

edited

Loading

jfortier-haptiq commented Aug 23, 2016 •

edited

Loading

dotannn commented Aug 23, 2016

srikiraju commented Aug 23, 2016

adamchenwei commented Aug 23, 2016

jfortier-haptiq commented Aug 23, 2016 •

edited

Loading

srikiraju commented Aug 23, 2016 •

edited

Loading

VictorSage commented Aug 23, 2016

prashanthparsi commented Aug 23, 2016

DVLP commented Aug 23, 2016

adamchenwei commented Aug 23, 2016

codingmaven commented Aug 23, 2016

prashanthparsi commented Aug 23, 2016 •

edited

Loading

rameshthoomu commented Aug 23, 2016

adamchenwei commented Aug 23, 2016

chrisbolin commented Aug 23, 2016

VictorSage commented Aug 23, 2016 •

edited

Loading

srikiraju commented Aug 23, 2016

DVLP commented Aug 23, 2016 •

edited

Loading

quantizor commented Aug 23, 2016

robwalch commented Aug 23, 2016

zkat commented Aug 23, 2016

adamchenwei commented Aug 23, 2016 •

edited

Loading

zkat commented Aug 23, 2016

seldo commented Aug 23, 2016

jokeyrhyme commented Aug 24, 2016

YurySolovyov commented Aug 24, 2016 •

edited

Loading

npm install error - No compatible version found: fs@0.0.2 #13743

npm install error - No compatible version found: fs@0.0.2 #13743

Comments

dotannn commented Aug 23, 2016

I'm opening this issue because:

What's going wrong?

supporting information:

adamchenwei commented Aug 23, 2016 • edited Loading

jfortier-haptiq commented Aug 23, 2016 • edited Loading

dotannn commented Aug 23, 2016

srikiraju commented Aug 23, 2016

adamchenwei commented Aug 23, 2016

jfortier-haptiq commented Aug 23, 2016 • edited Loading

srikiraju commented Aug 23, 2016 • edited Loading

VictorSage commented Aug 23, 2016

prashanthparsi commented Aug 23, 2016

DVLP commented Aug 23, 2016

adamchenwei commented Aug 23, 2016

codingmaven commented Aug 23, 2016

prashanthparsi commented Aug 23, 2016 • edited Loading

rameshthoomu commented Aug 23, 2016

adamchenwei commented Aug 23, 2016

chrisbolin commented Aug 23, 2016

VictorSage commented Aug 23, 2016 • edited Loading

srikiraju commented Aug 23, 2016

DVLP commented Aug 23, 2016 • edited Loading

quantizor commented Aug 23, 2016

robwalch commented Aug 23, 2016

zkat commented Aug 23, 2016

adamchenwei commented Aug 23, 2016 • edited Loading

zkat commented Aug 23, 2016

seldo commented Aug 23, 2016

jokeyrhyme commented Aug 24, 2016

YurySolovyov commented Aug 24, 2016 • edited Loading

adamchenwei commented Aug 23, 2016 •

edited

Loading

jfortier-haptiq commented Aug 23, 2016 •

edited

Loading

jfortier-haptiq commented Aug 23, 2016 •

edited

Loading

srikiraju commented Aug 23, 2016 •

edited

Loading

prashanthparsi commented Aug 23, 2016 •

edited

Loading

VictorSage commented Aug 23, 2016 •

edited

Loading

DVLP commented Aug 23, 2016 •

edited

Loading

adamchenwei commented Aug 23, 2016 •

edited

Loading

YurySolovyov commented Aug 24, 2016 •

edited

Loading