We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am not sure when this behavior started. It def exists in node 5.6.0 with npm 3.7.5.
When doing "npm init" the default format for the "repository" url starts with git+
git+
Example, edited for brevity. Showing only what is set by the "git repository" question.
$ npm init git repository: https://github.com/cnnlabs/something.git About to write to /Users/jyoung/dev/test/package.json: { "repository": { "type": "git", "url": "git+https://github.com/cnnlabs/something.git" }, "bugs": { "url": "https://github.com/cnnlabs/something/issues" }, "homepage": "https://github.com/cnnlabs/something#readme" }
ESDoc pulls the repository.url for the href of the "Repository" link, which is invalid since it starts with git+.
repository.url
It would be more appropriate to pull the homepage property.
homepage
The text was updated successfully, but these errors were encountered:
Changing this to read from homepage will probably break more people than are currently broken using git+ urls with the repository property.
repository
Sorry, something went wrong.
fix(publisher): broken repository url
5713d1e
#235
Thanks this issue. I released the v0.4.6 that fixes this bug.
No branches or pull requests
I am not sure when this behavior started. It def exists in node 5.6.0 with npm 3.7.5.
When doing "npm init" the default format for the "repository" url starts with
git+
Example, edited for brevity. Showing only what is set by the "git repository" question.
ESDoc pulls the
repository.url
for the href of the "Repository" link, which is invalid since it starts withgit+
.It would be more appropriate to pull the
homepage
property.The text was updated successfully, but these errors were encountered: