strongloop/strong-globalize

npm ci/install fails with error trying to fetch strong-globalize@4.1.4

santhoshscs opened this issue · 5 comments

I am facing one issue with a project when building with node 8.16.0 - This build was working without any issues for some time -

$ npm ci
npm WARN prepare removing existing node_modules/ before installation
npm ERR! code E404
npm ERR! 404 Not Found: strong-globalize@4.1.4

this version 4.1.4 is not available in the npm repository .
see
Screen Shot 2019-07-19 at 4 51 28 PM

But I can see a time stamp for this version in http://registry.npmjs.com/strong-globalize

Screen Shot 2019-07-19 at 4 50 00 PM

@santhoshscs , i think @raymondfeng had unpublished some version of strong-globalize at some point but didn't recall which version exactly.
Do you have package-lock.json in your application that's why it's specifically asking for 4.1.4? If so, could you please remove this file and remove the node_modules folder and run npm i again.
Hope it helps.

Running into a similar issue when trying to install IBM's API Connect cli from npm

$ npm install -g apiconnect                                                                    
npm WARN deprecated @angular/http@2.4.10: Switch to @angular/common/http - see https://angular.io/guide/http
npm WARN deprecated angular-ui-router@0.2.18: This npm package 'angular-ui-router' has been renamed to '@uirouter/angularjs'. Please update your package.json. See https://ui-router.github.io/blog/uirouter-scoped-packages/
npm WARN deprecated buildmail@4.0.1: This project is unmaintained
npm WARN deprecated crypto@0.0.3: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.
npm ERR! code ETARGET
npm ERR! notarget No matching version found for strong-globalize@4.1.4
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

@alessfg , we're working with the APIConnect team on a resolution.

apiconnect@5.0.25 is out that has resolved this issue.
@santhoshscs, I'm not sure if you get this issue from apiconnect module. If not, install the dependencies again and your problem should be fixed. Thanks.