-
Notifications
You must be signed in to change notification settings - Fork 182
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
Scoped packages (e.g. @ds/package1) cause Docusaurus 404s #248
Comments
hello.. i have had a quick look to try and replicate but will need a bit more time. I don't suppose your repo is public by any chance? |
@tgreyuk sorry for the delay, I've put together a repository that works in the same way as our internal repository: https://github.com/sstone1/typedoc-plugin-markdown-issue-248
You'll find all the files created start with an underscore, which will cause Docusaurus to ignore them:
|
@sstone1 thanks for detailed repo and apologies it took so long to get around to this one. typedoc-plugin-markdown@3.11.2 will remove the leading underscores. The syntax for packages in typedoc 0.22 is now:
Let me know if you still have issues. |
Thanks @tgreyuk, just tried it locally and it works perfectly! |
I have several packages I'm trying to generate documentation for.
These packages are all scoped, so in my case have names starting with "@ds/".
I am using the following Docusaurus config with this plugin:
It works fine and seems to generate all of the expected Markdown files.
The problem is that all of the files are prefixed with an underscore
_
, and Docusaurus returns 404 when I to visit any of them. This is usingdocusaurus start
so it's not a GitHub Pages + Jekyll thing, although the behaviour is similar.The files I get look like:
I assume the prefixed
_
is the replacement for the@
in the scoped package name.I also get warnings from Docusaurus about unresolvable links:
If I remove the prefixed
_
from the file names and fix up the links, things start to work, but it's not ideal!Any ideas? Sorry if I've made something confusing whilst trying to obscure package names and such.
The text was updated successfully, but these errors were encountered: