Build fails with Cannot destructure property `themeConfig` of 'undefined' or 'null'.
See original GitHub issueBug Report
Describe the bug
The build fails with Cannot destructure property
themeConfig of 'undefined' or 'null'.
. It works fine on the local dev server.
To Reproduce
- Go to https://utopian-train.surge.sh
- You will see the error message
Here’s the repo https://github.com/viewstools/docs/tree/docz.
Expected behavior
That the build works.
Environment
- OS: N/A
- Node/npm version: N/A
Additional context/Screenshots
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (1 by maintainers)
Top Results From Across the Web
Jest with Vue3 ERROR: Cannot destructure property 'config' of ...
On the project, I used Vue3, Vite, Typescript and testing tool Jest. I found only 1 solution to fix this. I have the...
Read more >Cannot destructure property 'prisma__type' of 'object null' as ...
When we try to execute the prisma raw query this error is coming in aws lambda dev server. But in local docker seems...
Read more >Theme configuration - Docusaurus
image, string, undefined, The meta image URL for the site. ... You can add items to the navbar via themeConfig.navbar.items .
Read more >[next.js] Cannot destructure property 'BACKEND_URL ... - GitLab
I have an app that's written in next.js, that has env variables. App works perfectly locally ( yarn dev, yarn build, yarn start, ......
Read more >TypeError: Cannot destructure property 'interface' of 'require ...
While testing the solidity contract, I'm getting the error `const { interface, bytecode } ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@pedronauck I am getting the same error in 0.13.7 with the default theme:
This happens as soon as I import a component.
I am using Typescript with create-react-app in a monorepo.
Same problem as @sbaechler. We love docz, but this prevents our frontend engineers to work 😦