No Longer Available on NPM about d HOT 10 CLOSED

@medikoo My problem has been solved.
The package doesn't exist in our company's depository. I used other depository to complete the update.
thank you！

from d.

Why did you assume that? d is in npm registry as it always was: https://www.npmjs.com/package/d

from d.

npm WARN deprecated [email protected]: Package no longer supported. Contact [email protected] for more info.

npm ERR! code ETARGET
npm ERR! notarget No matching version found for [email protected].
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'venona-specs-tools'
npm ERR! notarget

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/p2813835/.npm/_logs/2020-06-25T20_11_16_625Z-debug.log

npm debug log

1425 silly fetchPackageMetaData error for d@^1.0.1 No matching version found for D@^1.0.1.

We were using memoize, which required d.

However, because of d no longer existing in NPM, we had to replace all our usage of memoizee with mem. Multiple teams at my company are having to do the same thing.

from d.

Sorry to waste your time! You were right, was a registry issue. We use Artifactory, which mirrors NPM. Someone in the company uploaded a package called d with version 1.0.1. And thus, they broke everyone's repos in the whole company 😂.

from d.

@mssngr thanks for feedback. Good to see you've coined the source of the issue

from d.

I'm getting this exact same error but with "npm install gulp-cli". I fail to believe gulp let this break their code, but I can't see how to remove the dependency before install

from d.

There is no problem using NPM version 6+, but in npm7, there will be errors when updating.

from d.

@hanweiit007 this package is named d not D

from d.

I didn't add [email protected] dependency, It is dependent on gulp.

from d.

@hanweiit007 d and D are different packages. Your first comment lists D.

If your package manager installed D instead of d where it's d that's expected then it's a bug in package manager and it should be reported in its issue tracker.

from d.