Error Building static HTML failed for path "/home/" #12706
Comments
|
Solved it error Building static HTML failed for path "/404/"
See our docs page on debugging HTML builds for help https://gatsby.dev/debug-html
8 | else
9 | root["lib"] = factory(root["@reach/router"], root["core-js/modules/es6.array.iterator"], root["core-js/modules/es6.array.sort"], root["core-js/modules/es6.function.name"], root["core-js/modules/es6.map"], root["core-js/modules/es6.object.assign"], root["core-js/modules/es6.object.to-string"], root["core-js/modules/es6.regexp.constructor"], root["core-js/modules/es6.regexp.split"], root["core-js/modules/es6.regexp.to-string"], root["core-js/modules/es6.string.ends-with"], root["core-js/modules/es6.string.iterator"], root["core-js/modules/web.dom.iterable"], root["crypto"], root["fs"], root["lodash"], root["path"], root["react"], root["react-dom/server"], root["react-helmet"]);
> 10 | })(this, function(__WEBPACK_EXTERNAL_MODULE__reach_router__, __WEBPACK_EXTERNAL_MODULE_core_js_modules_es6_array_iterator__, __WEBPACK_EXTERNAL_MODULE_core_js_modules_es6_array_sort__, __WEBPACK_EXTERNAL_MODULE_core_js_modules_es6_function_name__, __WEBPACK_EXTERNAL_MODULE_core_js_modules_es6_map__, __WEBPACK_EXTERNAL_MODULE_core_js_modules_es6_object_assign__, __WEBPACK_EXTERNAL_MODULE_core_js_modules_es6_object_to_string__, __WEBPACK_EXTERNAL_MODULE_core_js_modules_es6_regexp_constructor__, __WEBPACK_EXTERNAL_MODULE_core_js_modules_es6_regexp_split__, __WEBPACK_EXTERNAL_MODULE_core_js_modules_es6_regexp_to_string__, __WEBPACK_EXTERNAL_MODULE_core_js_modules_es6_string_ends_with__, __WEBPACK_EXTERNAL_MODULE_core_js_modules_es6_string_iterator__, __WEBPACK_EXTERNAL_MODULE_core_js_modules_web_dom_iterable__, __WEBPACK_EXTERNAL_MODULE_crypto__, __WEBPACK_EXTERNAL_MODULE_fs__, __WEBPACK_EXTERNAL_MODULE_lodash__, __WEBPACK_EXTERNAL_MODULE_path__, __WEBPACK_EXTERNAL_MODULE_react__, __WEBPACK_EXTERNAL_MODULE_react_dom_server__, __WEBPACK_EXTERNAL_MODULE_react_helmet__) {
| ^
11 | return
WebpackError: Invariant Violation: Minified React error #130; visit https://reactjs.org/ docs/error-decoder.html?invariant=130&args[]=object&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
- universalModuleDefinition:10 ba
lib/webpack/universalModuleDefinition:10:2
- bootstrap:33 a.render
lib/webpack/bootstrap:33:1
- bootstrap:30 a.read
lib/webpack/bootstrap:30:1
- bootstrap:42 renderToString
lib/webpack/bootstrap:42:1
- static-entry.js:206 Module.default
lib/.cache/static-entry.js:206:18
- bootstrap:24 Promise
lib/webpack/bootstrap:24:1
- gatsby-browser-entry.js:44 Promise._resolveFromExecutor
lib/.cache/gatsby-browser-entry.js:44:19
- bootstrap:68 new Promise
lib/webpack/bootstrap:68:1
- bootstrap:5 tryCatcher
lib/webpack/bootstrap:5:1
- bootstrap:50 MappingPromiseArray._promiseFulfilled
lib/webpack/bootstrap:50:1
- api-runner-ssr.js:6 MappingPromiseArray.PromiseArray._iterate
lib/.cache/api-runner-ssr.js:6:16
- bootstrap:67 MappingPromiseArray.init
lib/webpack/bootstrap:67:1
- bootstrap:19 MappingPromiseArray._asyncInit
lib/webpack/bootstrap:19:1
Below is the package.json of the last successful build { I found a solution to my problem and it was about my react component. Sorry about the additional post. I solved it by brute force, checked my github, and one by one disabled added components from the last successful built and found the culprit. Good luck ! |
sidharthachatterjee
added
the
type: question or discussion
|
@antonioc57 This typically occurs when there is an error during server side rendering in Based on your stack trace, it looks like it is coming from |
|
@antonioc57 , |
|
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! Thanks for being a part of the Gatsby community! 💪💜 |
gatsbot
bot
added
the
stale?
|
Hey again! It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing! Thanks again for being part of the Gatsby community! |
|
Got same error: dependencies I am using: |
Hey folks, I was getting the same issue then I removed the code of Suspense and Lazy load from my file. It worked! I hope it may work for you as well until they add the support for these. Happy Coding! |
|
i dont get, what code of suspense and lazy?? |
|
|
I got the same errror when I ran "gatsby build" , but it was working fine in development. I just changed it and added .default in the end like below & it started working fine. now I am adding my error detailso you can relate to it.
|
This is exactly what I was doing as well and this fixed the issue. Thank you! |
Hello, I have the error when I run the build, error has failed for the path, I have no idea where this error occurs.
The text was updated successfully, but these errors were encountered: