Skip to content

Retiring the Progress NPM Registry #712

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tsvetomir opened this issue Jul 3, 2017 · 20 comments
Closed

Retiring the Progress NPM Registry #712

tsvetomir opened this issue Jul 3, 2017 · 20 comments
Assignees

Comments

@tsvetomir
Copy link
Member

tsvetomir commented Jul 3, 2017

Starting from this week the Kendo UI for Angular packages will be published on npmjs.com to address the many concerns users were having with this distribution channel.

To switch to the default registry:

  1. Remove the following lines from your .npmrc file:

    @progress:registry=https://registry.npm.telerik.com/
    //registry.npm.telerik.com/:_authToken=<token>
    
  2. Delete package-lock.json and node_modules from your project, reinstall packages.

Please note that:

Edit (13/03/2018): Add info for package-lock.json, formatting.

@rvovard
Copy link

rvovard commented Jul 3, 2017

Installing Kendo UI for Angular packages from npmjs.com works, thank you.

But will it go on working as it is? I mean, packages are now available for free, openly. Is this the wanted behaviour or will there be future changes?

@tsvetomir
Copy link
Member Author

Packages are available without authentication, but the license still applies:

License

This is commercial software. To use it, you need to agree to the Telerik End User License Agreement for Kendo UI Complete. If you do not own a commercial license, this file shall be governed by the trial license terms.

All available Kendo UI commercial licenses may be obtained at http://www.telerik.com/purchase/kendo-ui.

@Jaygholap
Copy link

Have questions:
1.If you asking to remove two lines containing 'registry.npm.telerik.com' from .npmrc file then do we still need to keep .npmrc in project ? Because .npmrc contains only those lines with _authToken.
2.What about _authToken ? do we need to remove that as well ?
3.Can you give some example how this will work without _authToken in team project ?

@tsvetomir
Copy link
Member Author

@Jaygholap if that's all .npmrc contains then go ahead and remove it entirely.
The packages will be accessible with the default npm settings and no auth token.

@squadwuschel
Copy link

@Jaygholap is the a npm command how I can remove this from my global .npmrc file. Because we don't have any .npmrc in our project folders, it seems to be globaly stored for the current user.

Or where can I find this file on a windows 7 /10 pc

@tsvetomir
Copy link
Member Author

@squadwuschel it should be located at %USERPROFILE%\.npmrc

@JohannesHoppe
Copy link

I had to setup the Progress NPM Registry in multiple corporate environments, which was not funny.
Many thanks for this great discussion!

👍 👍 👍

@danobri
Copy link

danobri commented Jul 10, 2017

I have deleted the %USERPROFILE%\.npmrc file, and searched my machine for other instances, but still get the message saying to remove lines from my .npmrc file:

npm WARN deprecated @progress/[email protected]: The Progress NPM Registry has been retired in favor of npmjs.com. Please remove the two lines containing 'registry.npm.telerik.com' from your .npmrc file to start using the default registry. More details at https://goo.gl/rxe5Fd

I also tried rebooting, but am still getting the warning. Any idea why?

@tsvetomir
Copy link
Member Author

@danobri try running npm cache clean and remove your projects node_modules folder for good measure.

@danobri
Copy link

danobri commented Jul 10, 2017

Cache clean did it - thanks!

@yasiryc
Copy link

yasiryc commented Jul 17, 2017

I followed the steps above and cleaned .npmrc file. After cleaning the file, i used following command to install the grid but I got code 403 Forbidden error. Please note i am a licensed user.

npm install --save @progress/kendo-angular-grid @progress/kendo-angular-dropdowns @progress/kendo-angular-inputs @progress/kendo-angular-dateinputs @progress/kendo-data-query @progress/kendo-angular-intl @progress/kendo-angular-l10n @progress/kendo-drawing @progress/kendo-angular-excel-export @angular/animations

@tsvetomir
Copy link
Member Author

@yasiryc the public npm registry doesn't have authentication. It's likely that the npm cache or configuration is still pointing to the Progress registry.

Please run npm cache clean and remove the 'node_modules' folder from the project. If that fails, please open a support ticket and attach the npm-debug.log file for us to analyze.

@yasiryc
Copy link

yasiryc commented Jul 17, 2017

@tsvetomir Thank you for the feedback. I followed the steps and still no luck. I have opened support ticket and attached the log as well.

One thing i noticed in the log that 403 error was returned on following fetch request

65 http fetch GET 403 https://registry.npm.telerik.com/@progress%2fkendo-angular-buttons/-/kendo-angular-buttons-0.23.0.tgz 244ms
66 silly fetchPackageMetaData error for @progress/kendo-angular-buttons@https://registry.npm.telerik.com/@progress%2fkendo-angular-buttons/-/kendo-angular-buttons-0.23.0.tgz 403 Forbidden: @progress/kendo-angular-buttons@https://registry.npm.telerik.com/@progress%2fkendo-angular-buttons/-/kendo-angular-buttons-0.23.0.tgz

@brownieboy
Copy link

@yasiryc,

You are still pointing to the retired Telerik repository. You need to be pointing to the standard npmjs repository, e.g:

https://registry.npmjs.org/@progress/kendo-angular-buttons/-/kendo-angular-buttons-0.23.0.tgz

Did you follow all the instructions and suggestions in the previous posts on this thread?

@niklas-dahl
Copy link

this is a very appreciated change, since it makes installing kendo in a CI environment much easier 👍

will this also mean that Kendo UI Professional will become open source?

@tsvetomir
Copy link
Member Author

@niklas-dahl there are no plans for open sourcing the components at the moment.

Some packages, most notably the themes and kendo-intl are dual-licensed with a commercial and Apache 2.0 license.

@yasiryc
Copy link

yasiryc commented Jul 25, 2017

In my case package-lock,json file still had reference cached to old repository. I removed it and "npm install" command worked without any issues

@tsvetomir
Copy link
Member Author

Be advised that the Progress NPM registry will be shut down by the end of January due to infrastructure reorganization. Installation of @progress/kendo-* packages will fail if you reference registry.npm.telerik.com in .npmrc, package-lock.json or yarn.lock files.

Please, make sure that you have removed references to registry.npm.telerik.com by following the steps outlined above.

@mgupta1221
Copy link

@tsvetomir I have a Kendo UI complete license which got expired in Oct 2017. Can I download "KendoUI For Angular" packages and use them in my organization projects.?

@tsvetomir
Copy link
Member Author

@mohitgupta86 please open a support ticket for issues regarding licensing. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants