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
Uncaught (in promise) Error: page resources for / not found. Not rendering React #25342
Comments
This took a lot of tracking down.. finally figured it out. The module is throwing an error:
However I don't totally understand why this is happening yet |
We are chasing a similar error that says |
Like @GreenOn, I am also trying to debug In my case, /app/ is a client-only route that contains a client-side react app. I have no problems when I run Any suggestions on how to approach debugging this would be greatly appreciated. UPDATE: I just debugged `Uncaught (in promise) Error: page resources for /app/ not found. Turns out the problems was with react-contextmenu (vkbansal/react-contextmenu#284) which works fine client-side but breaks server-side during the gatsby build process. My temporary solution for now is to use the compiled version of react-contextmenu in So instead of The way I debugged this was by removing all components from my app component, then adding them back one at a time until I found the component that was breaking the build. |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
No, I am also facing the same issue and not able to find the solution for it. |
Yes, same here. It happens only in serve mode and when I pass a second time (or refresh) on the index page. |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
any idea how to solve this? |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
Solution for @react-spring/module@ahmadkhalaf1 @zgababa I have tried this solution and it worked for me: pmndrs/react-spring#1069 (comment) . However, first, make sure you don't have any hidden html-build errors. For example:
|
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
we have the issue for and we have sevaral page without any problem , the problematic one use hash to pass some more information |
Similarly to #19618 (comment) I'll close this as the original error was fixed as you'll now see a more detailed error. If you can provide a minimal reproduction (https://www.gatsbyjs.com/contributing/how-to-make-a-reproducible-test-case/) showing that it's an issue with Gatsby v3, please open a new issue. Thanks! |
Description
I'm trying to use Gatsby with react-spring and react-three-fiber. I'm able to successfully get my example code to work while in develop mode. However, after a build and serving that page, I get an in-browser console error.
**Uncaught (in promise) Error: page resources for / not found. Not rendering React
at production-app.js:128 **
There are no build errors. The problem is not present when I change a.mesh to mesh. That initially led me to believe that this is a React-Spring and or three-fiber problem (and it still may very well be), but after checking issues here, I see other Gatsby users having similar "Not rendering React" errors in the built version and thought it would be wise to check.
Steps to reproduce
Build a project with Gatsby, React-spring/three using <a.mesh>.
Minimal repo:
https://github.com/anim8rDev/meshError
Expected result
No errors and the Canvas properly rendered on the built project (again, it works fine in develop).
Actual result
Error:
**Uncaught (in promise) Error: page resources for / not found. Not rendering React
at production-app.js:128 **
Canvas does not render.
Environment
System:
OS: Windows 10 10.0.18362
CPU: (16) x64 AMD Ryzen 7 3700X 8-Core Processor
Binaries:
Node: 12.14.1 - D:\SOFTWARE\Applications\nodejs\node.EXE
npm: 6.13.4 - D:\SOFTWARE\Applications\nodejs\npm.CMD
Languages:
Python: 3.8.1
Browsers:
Edge: 44.18362.449.0
npmPackages:
gatsby: ^2.23.11 => 2.23.11
gatsby-plugin-root-import: ^2.0.5 => 2.0.5
npmGlobalPackages:
gatsby-cli: 2.12.37
The text was updated successfully, but these errors were encountered: