-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Docs] Add missing metadata in page “using-npm/semver” to fix broken links and nav #1572
Conversation
I just committed a small change in one of the Tap tests — the one checking documentation for semver. Tests pass now. |
@isaacs, am I missing any step here for the team to be able to review the PR? |
Awesome finding! 🙌 Thank you so much for the fix @tripu! |
PR-URL: #1572 Credit: @tripu Close: #1572 Reviewed-by: @ruyadorno
PR-URL: #1572 Credit: @tripu Close: #1572 Reviewed-by: @ruyadorno
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.
Pıroje takıpcıkazan
Excuse me, I'm not familiar with your workflow: when will this be deployed to This change does not show there yet, and I was wondering. |
Problem: there have been a number of broken links in
docs.npmjs.com
for quite some time now. At least hyperlinks to section Using npm / semver are broken.Examples: visit
docs.npmjs.com/configuring-npm/package-json
and on your browser find the stringSee semver
; there are 3 instances, all of them linking todocs.npmjs.com/using-npm/semver
, which does not exist.A related outstanding issue (I believe) is that such subsection (semver) does not appear in the index page of section Using npm.
Solution: after digging a bit in the docs and how they are built, I think the cause may be that this specific page is lacking some metadata at the beginning. Because of that, the page is not generated, indexed and/or copied to the output dir. After changing this, Gatsby seems to be serving the page OK, and it appears in the nav sidebar element.