-
Notifications
You must be signed in to change notification settings - Fork 3
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
Think about publishing packages to NPM registry instead of GitHub packages #20
Comments
lukas-schardt
pushed a commit
that referenced
this issue
Feb 19, 2021
lukas-schardt
pushed a commit
that referenced
this issue
Feb 24, 2021
lukas-schardt
pushed a commit
that referenced
this issue
Feb 24, 2021
lukas-schardt
pushed a commit
that referenced
this issue
Feb 24, 2021
lukas-schardt
pushed a commit
that referenced
this issue
Feb 24, 2021
lukas-schardt
pushed a commit
that referenced
this issue
Feb 25, 2021
lukas-schardt
pushed a commit
that referenced
this issue
Feb 25, 2021
lukas-schardt
pushed a commit
that referenced
this issue
Feb 25, 2021
lukas-schardt
pushed a commit
that referenced
this issue
Feb 25, 2021
lukas-schardt
pushed a commit
that referenced
this issue
Feb 25, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As I found out today it is not possible at the moment to read npm packages from the GitHub Packages registry without a personal access token. Even for public repositories/packages...
This is very unfortunate...
By digging deeper I found that this will probably not be solved in the near future: https://github.saobby.my.eu.orgmunity/t/download-from-github-package-registry-without-authentication/14407
So maybe we should start publishing to the real NPM registry ?
This would also resolve #17
cc @quarkus @lukas-schardt @KinG-DE
The text was updated successfully, but these errors were encountered: