-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
fix: escaped slash in namespaced packages #2193
fix: escaped slash in namespaced packages #2193
Conversation
…packages' into fix/escaped-slash-in-namespaced-packages
* chore: fix start web issue * chore: use custom action for changeset this is temporary while I find the way to skip create github releases for alpha * chore: format as separated workflow (#2194) Co-authored-by: Juan Picado <juanpicado19@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @amitgilad3 great stuff 💯
could you add a changeset https://github.com/verdaccio/verdaccio/blob/master/CONTRIBUTING.md#adding-a-changeset ? Then we are good to merge. |
One more thing, this won't be available on Verdaccio 5 after merge this, if you want to also be avilable there, then you would need a new PR over 5.x branch. |
* chore: fix start web issue * chore: use custom action for changeset this is temporary while I find the way to skip create github releases for alpha * chore: format as separated workflow (#2194) Co-authored-by: Juan Picado <juanpicado19@gmail.com>
…n-namespaced-packages
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Welcome to verdaccio world @amitgilad3 🚀 |
thanks!!!!! @juanpicado , i hope to contribute as much as possible to this amazing product!!! |
@juanpicado Has this been merged in v5? |
Nop, only master by far (for v5 should be on 5.x branch) |
in order to fix the escaped slash and make it more like the response from npm registry i removed the encodeScopedUri function which replaces in scoped url the / with %2f making in compatible with the response from npm
close #1778 #1777