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
It's common for README.md files to link to other markdown files. On GitHub, when you click one of those links it will take you to a page with the markdown rendered instead of the source code for the markdown file. On JSR, those links take you to the source code for the markdown files.
You can see an example of this by clicking any of the links near the bottom of the overview for my package.
This problem is compounded further if the package is published out of a monorepo / workspace. What happens is the linked repository is the workspace root, and the links to the markdown docs are generated relative to that, not relative to the package subdirectory in that root.
The package markdown should render relative links that stay on the jsr site, and show the file in the files view, imo
It's common for README.md files to link to other markdown files. On GitHub, when you click one of those links it will take you to a page with the markdown rendered instead of the source code for the markdown file. On JSR, those links take you to the source code for the markdown files.
You can see an example of this by clicking any of the links near the bottom of the overview for my package.
https://jsr.io/@udibo/react-app
The text was updated successfully, but these errors were encountered: