-
Notifications
You must be signed in to change notification settings - Fork 69
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
package.json
repository field
#212
Comments
Can you elaborate on how this is impacting your workflow, please? |
yarn-plugin-outdated's purpose is to display a list of outdated NPM packages. As part of that, it parses packages' Since Vision's repository is unusable, this feature of yarn-plugin-outdated doesn't work for it. |
Alright, thank you for the details. We'd have to investigate more to know where the problem comes from. I believe |
Thanks for the reply. It's my understanding that the On the other hand, I'm taking a closer look at my node_modules tree now, and there are several |
It could just be because
In any case it is an incorrect outdated repo link to include in the |
FYI this is an issue across the hapijs ecosystem, and eg. hapi itself has a bad value. It seems that inert is fine, since I apparently had the prescience to update it 5 years ago: hapijs/inert@dfcd066 |
We can also have it as: {
"repository": {
"type": "git",
"url": "https://github.com/hapijs/vision.git"
}
} As shown here: https://docs.npmjs.com/cli/v8/configuring-npm/package-json#repository. |
Support plan
Context
What are you trying to achieve or the steps to reproduce?
Vision's package.json's
repository
field is apparently incorrect. It saysgit://github.com/hapijs/vision
; however, as far as I know, GitHub doesn't support thegit://
URL scheme. Instead, it should be https://github.com/hapijs/vision.git.What was the result you got?
Non-functioning repository
What result did you expect?
Usable repository
The text was updated successfully, but these errors were encountered: