Kendo-angular: npm ERR! 404 no such package available : @telerik/kendo-inputs-common

Created on 20 Sep 2016  路  6Comments  路  Source: telerik/kendo-angular

Error happens when attempting to install kendo-angular-inputs.

npm ERR! 404 no such package available : @telerik/kendo-inputs-common npm ERR! 404 npm ERR! 404 '@telerik/kendo-inputs-common' is not in the npm registry. npm ERR! 404 You should bug the author to publish it (or use the name yourself!) npm ERR! 404 It was specified as a dependency of '@progress/kendo-angular-inputs ```'

Most helpful comment

@tsvetomir It's not, that's exactly the problem. Nice work. I just ran npm config set "@telerik:registry" http://registry.npmjs.org/ and it is now working like a charm.

All 6 comments

Looks like this is also happening with dropdowns.

npm ERR! 404 no such package available : @telerik/kendo-dropdowns-common
npm ERR! 404
npm ERR! 404 '@telerik/kendo-dropdowns-common' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of '@progress/kendo-angular-dropdowns'

Looks like it's happening with quite a few others. What is available looks great, looking forward to more!

Looks like the package is available here:

https://www.npmjs.com/package/@telerik/kendo-inputs-common

Which version of the package are you using? Make sure you have the correct npm registry set.

Update - Just tested it in a sample project and it seems to be working.

Make sure your main registry is npmjs.org:
npm set registry https://registry.npmjs.org/

From getting started:

Note that the Progress NPM registry is designed to work as a scoped registry. This is important to understand because if you set it as a main registry by mistake, the access to the official registry (https://registry.npmjs.org/) will be blocked.

I'm just running npm install -S @progress/kendo-angular-inputs. I'm going to update to node 5 now to confirm that's not the problem. I'm currently on 4.4.3.

@tsvetomir It's not, that's exactly the problem. Nice work. I just ran npm config set "@telerik:registry" http://registry.npmjs.org/ and it is now working like a charm.

Was this page helpful?
0 / 5 - 0 ratings