Closed SayuShira closed 7 months ago
I randomly looked into this again, since there were a few updates. My issue didn't go away from that, but I stumbled upon the # in my path. I tried without and ... it works. Yeah, stupid easy "fix". My bad. Closing this.
Hey! I'm having trouble running this locally on Windows.
I get the following error upon
pnpm start
.Looking into
.docusaurus
the files appear to be there under.docusaurus/docusaurus-plugin-content-blog/default
just like the doc files are under.docusaurus/docusaurus-plugin-content-docs/default
. Or some meta files, not the full content.What I tried:
pnpm build
but its missing the version defining file and didn't lead anywheredocusaurus.config.js
presetspnpm ci
it didn't loadYes, just trying everything..
Next day me cloned the project to WSL and it kinda ran there. Another, new, error showed, but was a relatively simple fix (faq imported
Constructor
instead ofconstructor
). Here the website loaded, displaying an overlay with the errors.I went back to windows to try more and found that if i manually edit
?truncated=true
out of the.docusaurus/registry.js
it loads everything just fine. The problem is that this file is recreated everypnpm start
. So far I'm unable to find a config option that would stop docusaurus from adding?truncated=true
.Maybe I am just missing something? Do you have any ideas? Did anyone successfully run it on windows? Might also just be a alpha/beta thing with windows.
Thanks for reading so far in any case.
Side note: As mentioned I tried updating docusaurus (v3alpha -> v3beta). With the beta running the compilation has one more error. See below. At least this was a fast and easy fix >.<
Above errors appeared as well on windows. The compilation error below does happen on WSL too.
Curiously windows only printed one of these errors. This below is from WSL. Sadly the differentiating part of the file path (again
?truncated=true
) is only visible on the overlay error on the webpage, which doesn't load on windows.