-
Notifications
You must be signed in to change notification settings - Fork 215
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
Comments
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? |
Packages are available without authentication, but the license still applies: LicenseThis 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. |
Have questions: |
@Jaygholap if that's all |
@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 |
@squadwuschel it should be located at |
I had to setup the Progress NPM Registry in multiple corporate environments, which was not funny. 👍 👍 👍 |
I have deleted the
I also tried rebooting, but am still getting the warning. Any idea why? |
@danobri try running |
Cache clean did it - thanks! |
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.
|
@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 |
@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 |
You are still pointing to the retired Telerik repository. You need to be pointing to the standard npmjs repository, e.g: Did you follow all the instructions and suggestions in the previous posts on this thread? |
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? |
@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. |
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 |
Be advised that the Progress NPM registry will be shut down by the end of January due to infrastructure reorganization. Installation of Please, make sure that you have removed references to registry.npm.telerik.com by following the steps outlined above. |
@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.? |
@mohitgupta86 please open a support ticket for issues regarding licensing. Thanks! |
Uh oh!
There was an error while loading. Please reload this page.
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:
Remove the following lines from your
.npmrc
file:Delete
package-lock.json
andnode_modules
from your project, reinstall packages.Please note that:
Edit (13/03/2018): Add info for package-lock.json, formatting.
The text was updated successfully, but these errors were encountered: