You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, clicking on these links does nothing - it looks like whatever markdown-to-HTML converter is being used doesn't include the anchor elements which would cause the page to scroll down to the linked topic.
The text was updated successfully, but these errors were encountered:
That is interesting. I don't know if I can do anything about how npmjs.com processes my original markdown. For now, it would be best to go directly to the original at
Thanks that's helpful, I didn't know about that link. One suggestion, then, would be to embed the canonical doc link into the doc somewhere, so that when it shows up on npmjs.com, people can click on it to go to the github page and get the better experience.
That's a good idea! I hadn't thought about how people would land on the npm page first, and not realize it was a slightly imperfect copy of the original documentation.
On the npmjs.com page (https://www.npmjs.com/package/astronomy-engine) there are a lot of links which have UR: fragment identifiers:
However, clicking on these links does nothing - it looks like whatever markdown-to-HTML converter is being used doesn't include the anchor elements which would cause the page to scroll down to the linked topic.
The text was updated successfully, but these errors were encountered: