-
-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
docusaurus-start doesn't work with projects that contain "pages" in their path #2016
Comments
hi @endiliey i'm facing this issue, how do i fix it?? |
@Boluwatifeh unfortunately he won't answer: https://v2.docusaurus.io/blog/2020/01/07/tribute-to-endi I'm working on v2, which is not far from a stable release, so it's worth considering migrating. i18n, the last missing feature for beta/RC/GA, is coming soon. |
Ohh @slorber I'm deeply sorry about what happened. So there's no fix for the issue until a beta us being released? |
I think this should work in v2 and you shouldn't wait for v2 beta to try using it as it's quite stable already. v1 do not receive many bugfixes atm as I'm working only v2. If you want this fixed on v1 soon, the best way is likely to send a PR. |
@slorber I'm facing the issue with v2. I tried running npm start after following the instructions from the docusaurus v2 website. I got the error "LiveReload server started on port 35729 |
So you should open a separate issue with v2, and proper repro steps (ideally a github repo) and error messages. This issue was for v1, so if you have it with v2, I need at least the error message from v2. |
Okay, I'd do that right away. Thanks |
π Bug Report
Dev server crashes on file copy of files that contain
pages
in their path.server.js
grabs an incorrect path:Have you read the Contributing Guidelines on issues?
Yes
To Reproduce
Expected behavior
Dev server should start successfully.
Actual Behavior
Dev server doesn't start.
The text was updated successfully, but these errors were encountered: