Kendo-angular: NPM issue - @progress/kendo-angular-dropdowns now only has the version version 0.1.0

[masterjs]

Hello,
Our entire build process now stopped working because the @progress/kendo-angular-dropdowns versions are no longer available. The command npm view @progress/kendo-angular-dropdowns versions --json is now only returning the version 0.1.0 compared to multiple in the past (like 1.0.10).

Anything can be done on your side to fix this (really soon..)?

thank you,
JS

[abhissha]

We run into the same issue with only version 0.1.0 showing on the kendo repository.

[tsvetomir]

The issue should be fixed now, apologies for the inconvenience.

[masterjs]

I confirm that its now working, thank you for the fast response, really appreciated.

JS

[masterjs]

Ok, spoke too soon, now they are in fact available, but I keep on getting integrity issues now:

npm ERR! shasum check failed for C:\Users\SVC-TF~2\AppData\Local\Temp\npm-26016-5e341f22\registry.npm.telerik.com_40progress_252fkendo-angular-dropdowns-\kendo-angular-dropdowns-1.0.10.tgz
npm ERR! Expected: 54fa32b72bead69eae4d16a6af30837565214e27
npm ERR! Actual: af13cb751e62e1bf35621c4f8c4d2fdf7d07ab49
npm ERR! From: https://registry.npm.telerik.com/@progress%2fkendo-angular-dropdowns/-/kendo-angular-dropdowns-1.0.10.tgz

Is there still an issue on your side?

JS

[tsvetomir]

We had to republish the affected versions and the SHAs will be different. You'll need to delete your package-lock.json file if you're using npm 5. Sorry!

[masterjs]

Hello @tsvetomir ,
I do not keep package-lock.json on the build server and it runs on npm 4.2. Know any other way around this issue or are you sure the the repository publishes the right sha?

[talynone]

Same issues, I updated to npm5 from npm3 and didn't help. Now get this error :
npm ERR! code EINTEGRITY npm ERR! sha1-4OGzRL1H8dULW1qwPZNffCBNUrg= integrity checksum failed when using sha1: wanted sha1-4OGzRL1H8dULW1qwPZNffCBNUrg= but got sha1-6NZO/nltbKXAhb/ugnirSiPoB0A=. (141963 bytes)

[amartinelli6577]

Same issues here as well. shasum check keeps failing. I've tried this with npm versions 5.0.3, 4.6.1, and 3.10.10.

[masterjs]

I also just for the fun tried
"@progress/kendo-angular-dropdowns": "http://registry.npm.telerik.com/@progress%2fkendo-angular-dropdowns/-/kendo-angular-dropdowns-1.0.11.tgz"
in my package.json, but this times-out... so no luck there. :o(

JS

[tsvetomir]

We released an updated version that should not have the checksum issue. To get it run:

npm install --save @progress/kendo-angular-dropdowns@^1.1.0

Older versions are not yet restored, we'll continue that effort. Sorry everyone!

[masterjs]

Hello @tsvetomir,
Thank you. I'm confirming that the full process is now working with v 1.1.0.

JS

[Quovadisqc]

Hi @tsvetomir

Is there any ETA on when the @ng2 packages will be fixed?

Thanks!

[whuang02]

I'm having a separate issue where I'm getting a 404 Not found for the @telerik/kendo-dropdowns-common dependency when I try to install the dropdown module.

107 http 404 http://registry.npmjs.org/@telerik%2fkendo-dropdowns-common
108 verbose headers { date: 'Thu, 22 Jun 2017 21:19:12 GMT',
108 verbose headers   'content-type': 'application/json',
108 verbose headers   'content-length': '21',
108 verbose headers   connection: 'keep-alive',
108 verbose headers   'cache-control': 'max-age=0',
108 verbose headers   'accept-ranges': 'bytes',
108 verbose headers   via: '1.1 varnish',
108 verbose headers   age: '0',
108 verbose headers   'x-served-by': 'cache-ord1724-ORD',
108 verbose headers   'x-cache': 'MISS',
108 verbose headers   'x-cache-hits': '0',
108 verbose headers   'x-timer': 'S1498166352.307235,VS0,VE399' }
109 silly get cb [ 404,
109 silly get   { date: 'Thu, 22 Jun 2017 21:19:12 GMT',
109 silly get     'content-type': 'application/json',
109 silly get     'content-length': '21',
109 silly get     connection: 'keep-alive',
109 silly get     'cache-control': 'max-age=0',
109 silly get     'accept-ranges': 'bytes',
109 silly get     via: '1.1 varnish',
109 silly get     age: '0',
109 silly get     'x-served-by': 'cache-ord1724-ORD',
109 silly get     'x-cache': 'MISS',
109 silly get     'x-cache-hits': '0',
109 silly get     'x-timer': 'S1498166352.307235,VS0,VE399' } ]
110 silly fetchPackageMetaData Error: Not found : @telerik/kendo-dropdowns-common

Any suggestions for this?

[tsvetomir]

@Quovadisqc @whuang02 please try downloading the package again. Apologies.

[whuang02]

Hi @tsvetomir,

I'm still getting a 404 for the @telerik/kendo-dropdowns-common package.
When I go to: http://registry.npmjs.org/@telerik%2fkendo-dropdowns-common, I also see a 404 Not Found.

[tsvetomir]

The @telerik/kendo-dropdowns-common package is hosted on http://npmjs.org and shouldn't be affected by this outage. Try running npm cache clean and npm install to see if it isn't a cache issue.

[whuang02]

Cleaning the cache doesn't fix the issue.

I'm able to download regular packages from npmjs.org, but it seems that all scoped packages are giving me a 404.

I thought it was an issue with scoped packages, but strangely, I'm able to download scoped packages from registry.npmjs.telerik.org

[tsvetomir]

How about other scoped packages from npmjs.org such as @angular/core and @telerik/semantic-prerelease?

[masterjs]

@whuang02 is it possible that you have caching issues? I just did http://registry.npmjs.org/@telerik%2fkendo-dropdowns-common and I got a HTTP 200

[whuang02]

@tsvetomir other scoped packages even @angular/core, common, etc are failing
@masterjs I've tried cleaning the cache and removing node_modules no luck with that.

Is there anyway I can just manually install the @telerik/kendo-dropdowns-common, so I can download the @progress/kendo-angular-dropdowns module?

It's able to properly resolve the @progress/kendo-angular-dropdowns module, but fails once it reaches the dependency.

[masterjs]

@whuang02 you could "maybe" try https://registry.npm.telerik.com/@progress%2fkendo-angular-dropdowns/-/kendo-angular-dropdowns-1.0.10.tgz and replace the tarball with the expected version. That is something that is not working on my build server for unknown reason, but locally its ok.

[tsvetomir]

@masterjs try deleting the _node_modules_ folder and running npm cache clean for good measure.

[masterjs]

@tsvetomir I believe you meant @whuang02 ;o)

[whuang02]

@masterjs

Thanks I'm able to manually install the dependencies using the tarbell URLs.
I can now install the dropdown module thanks.

I think the 404 issue is caused by the '/' encoding not working properly.

It's hitting 'https://registry.npmjs.org/@telerik/kendo-dropdowns-common' rather than 'https://registry.npmjs.org/@telerik%2fkendo-dropdowns-common'

[whuang02]

Found out this issue was caused by OpenDNS redirections... The '%2f' gets resolved into a '/' during redirection.