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
In version 44 a failed import reports an error but docusaurus continues to run and reload changes. In 48 the server terminates and has to be restarted after the error is fixed. This is quite inconvenient during the development/documentation cycle.
Note that the example project below is using Lerna. This is just to make the repro easier -- our actual project doesn't use Lerna but exhibits the same behaviour.
Notice that the server starts, albeit with an error
Starting the development server...
× Client
Compiled with some errors in 8.43s
i 「wds」: Project is running at http://localhost:3001/
i 「wds」: webpack output is served from /
i 「wds」: Content not from webpack is served from D:\alfie\tmp\docusaurus-repro\packages\docusaurus-site
i 「wds」: 404s will fallback to /index.html
./docs/mdx.md
Module not found: Can't resolve '@theme/invalid' in 'D:\alfie\tmp\docusaurus-repro\packages\docusaurus-site\docs'
Kill the server
Edit package.json to upgrade to version 48. Re-run lerna bootstrap
Try to start docusaurus
Expected behavior
Docusaurus should start and report the import error.
Actual Behavior
Docusaurus reports the error and terminates.
Starting the development server...
* Client █████████████████████████ after emitting (98%)
i 「wds」: Project is running at http://localhost:3000/
i 「wds」: webpack output is served from /
i 「wds」: Content not from webpack is served from D:\alfie\tmp\docusaurus-repro\packages\docusaurus-site
i 「wds」: 404s will fallback to /index.html
Client bundle compiled with errors therefore further build is impossible.
Your Environment
Docusaurus version used: 2.0.0-alpha.48
Environment name and version (e.g. Chrome 78.0.3904.108, Node.js 10.17.0):
🐛 Bug Report
In version 44 a failed import reports an error but docusaurus continues to run and reload changes. In 48 the server terminates and has to be restarted after the error is fixed. This is quite inconvenient during the development/documentation cycle.
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce
Note that the example project below is using Lerna. This is just to make the repro easier -- our actual project doesn't use Lerna but exhibits the same behaviour.
lerna bootstrap
cd docusaurus-site
npm start
package.json
to upgrade to version 48. Re-runlerna bootstrap
Expected behavior
Docusaurus should start and report the import error.
Actual Behavior
Docusaurus reports the error and terminates.
Your Environment
Reproducible Demo
https://github.com/jugglingcats/docusaurus-repro
See above for detailed steps.
The text was updated successfully, but these errors were encountered: