-
-
Notifications
You must be signed in to change notification settings - Fork 8k
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
Brand new docusaurus installation not building #5287
Comments
Exactly the same error has also been to me! Is this a problem that only occurs in the latest version? |
Fixed in #5270. If you want to try that latest patched version, use the canary release |
@Josh-Cena I was able to reproduce this using a fresh npm @docusaurus/init of alpha.72. It looks like a bunch of babel packages were updated a few hours ago, likely the culprit but I haven't been able to pin down which. |
Errr... By "reproduce" you mean "make the links work" or "make them not work"? |
Make it not work, with a fresh install no modifications. I added all babel resolutions to not allow any of them to fetch the latest and it works now. Can try to figure out which in particular did it, but it's definitely a babel issue that is being propagated to docusaurus.
|
For one thing, the bug should be fixed by the latest canary release already. Also, alpha-72 sounds pretty ancient, and it's better to reproduce the bug on newer versions than older ones |
Error still persists after pulling from canary for me. |
If you can verify that your docusaurus version is |
This resolves the build error for me. |
I tried on the latest stable beta release first, as the issue creator did and noted above, and I got the same error. I then tried on alpha-72 to see if it was a docusaurus issue or a package issue because I knew alpha-72 didn't have the same problem. I suspect anyone installing fresh or upgrade packages will have the same problem because it seems to be a result of the latest babel which is fetched by a few docusaurus requirements. I was able to narrow it down to @babel/plugin-transform-react-display-name. Adding |
The temporary solution from @csestito works for me as well. Since the actual fix is already in the canary release and will probably make it onto prod soon I will close this issue for now. |
That's right, there was a bug in |
Thanks We are not alone having this issue 😅 Can confirm re-generating the lockfile should work, fix has been published 1h ago in @babel/plugin-transform-react-display-name@7.15.1 with PR babel/babel#13637 |
🐛 Bug Report
Prerequisites
npm run clear
oryarn clear
command.rm -rf node_modules yarn.lock package-lock.json
and re-installing packages.Description
Just created a new docusaurus installation following the getting started guide
Have you read the Contributing Guidelines on issues?
yep
Steps to reproduce
npx @docusaurus/init@latest init my-website classic
cd my-website && npm run start
Expected behavior
Expect build to succeed and the template docs to open up.
Actual behavior
The following error occurs when the build fails:
Your environment
Reproducible demo
Use https://new.docusaurus.io to create a CodeSandbox reproducible demo of the bug.
(Paste the link to an example repo, including a
docusaurus.config.js
, and exact instructions to reproduce the issue.)The text was updated successfully, but these errors were encountered: