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
[npm/yarn] InvalidPackageName #5246
Labels
Batch
How We Work: Feature. Outcome achieved within 1 iteration. Can live under an epic, or stand alone.
good first issue
L: javascript:npm
npm packages via npm
T: bug 🐞
Something isn't working
Comments
Thanks so much for reporting this issue, @Sergio-IME. I just opened PR #5259 with a fix. |
Thank you! |
Hello
looks like this
is rejected by this
|
abdulapopoola
added
the
Batch
How We Work: Feature. Outcome achieved within 1 iteration. Can live under an epic, or stand alone.
label
Mar 14, 2024
raj-meka
added a commit
that referenced
this issue
Apr 23, 2024
raj-meka
added a commit
that referenced
this issue
Apr 23, 2024
raj-meka
added a commit
that referenced
this issue
Apr 23, 2024
raj-meka
added a commit
that referenced
this issue
Apr 23, 2024
raj-meka
added a commit
that referenced
this issue
Apr 23, 2024
raj-meka
added a commit
that referenced
this issue
Apr 23, 2024
raj-meka
added a commit
that referenced
this issue
Apr 24, 2024
… as expected with proper validation
raj-meka
added a commit
that referenced
this issue
Apr 24, 2024
raj-meka
added a commit
that referenced
this issue
Apr 25, 2024
raj-meka
added a commit
that referenced
this issue
Apr 25, 2024
#5246:removing the leading underscore restriction in the package naming.
Thank you so much for reporting an issue @Sergio-IME i have raised PR #9569 with a fix |
Fixed in #9569 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Batch
How We Work: Feature. Outcome achieved within 1 iteration. Can live under an epic, or stand alone.
good first issue
L: javascript:npm
npm packages via npm
T: bug 🐞
Something isn't working
Hi
(sorry if this has to go to support instead of here, not quite sure)
it seems that this particular npm package is causing trouble in Insights > Dep graph > Dependabot tab, but maybe it has other ramifications
Package ecosystem
npm
Images of the diff or a link to the PR, issue, or logs
The text was updated successfully, but these errors were encountered: