I was following the tutorial and everything was going smoothly until I got to yarn redwood db save & yarn rw db up. Now the localhost is showing “Something Went Wrong”.
Running the command yarn rw g scaffold post partially works, while the about and home pages show “Something Went Wrong” if I navigate to http://localhost:8910/posts then the page renders. However, if I click “+New” or “Create one?” then the page reloads with “Something Went Wrong” again.
I had the problem with Redwood v0.2.4 & now v0.2.5 as well.
This post seems related but based on ^0.1.0 so I thought it would be best to bring it up again.
Please do see @rob’s reply asking about possible error messages. That info will help.
There’s definitely complexity involved in the process, which we are trying to find ways to improve on the DX side of things. So know your experience and questions are really important for us.
So far in most cases where the error is “Something went wrong”, there is an issue with the code and/or the db save and up commands not having been run since a change. This Issue thread (and my linked comment specifically) give some examples as well as a link to a repo with example “finished” code.
The above error occurred in the <RouterImpl> component:
in RouterImpl (created by LocationProvider)
in LocationProvider (created by Context.Consumer)
in Location (created by Router)
in Router (created by Routes)
in Routes
in ApolloProvider (created by GraphQLProvider)
in GraphQLProvider (created by RedwoodProvider)
in RedwoodProvider
in FatalErrorBoundary
React will try to recreate this component tree from scratch using the error boundary you provided, FatalErrorBoundary. react-dom.development.js:19560
React 18
logCapturedError
logError
payload
getStateFromUpdate
processUpdateQueue
resumeMountClassInstance
updateClassComponent
beginWork
beginWork$1
performUnitOfWork
workLoopSync
performSyncWorkOnRoot
scheduleUpdateOnFiber
updateContainer
legacyRenderSubtreeIntoContainer
unbatchedUpdates
legacyRenderSubtreeIntoContainer
render
js index.js:10
Webpack 7
__webpack_require__
fn
0
__webpack_require__
checkDeferredModules
webpackJsonpCallback
<anonymous>
console output after running yarn redwood dev is as follows:
yarn run v1.22.4
$ /Users/isaactait/Desktop/Coding/redwoodblog/node_modules/.bin/redwood dev
$ /Users/isaactait/Desktop/Coding/redwoodblog/node_modules/.bin/prisma2 generate --watch
$ /Users/isaactait/Desktop/Coding/redwoodblog/node_modules/.bin/webpack-dev-server --config ../node_modules/@redwoodjs/core/config/webpack.development.js
$ /Users/isaactait/Desktop/Coding/redwoodblog/node_modules/.bin/dev-server
13:58:29 db | Watching... /Users/isaactait/Desktop/Coding/redwoodblog/api/prisma/schema.prisma
13:58:29 db |
13:58:29 db | ✔ Generated Prisma Client to ./../node_modules/@prisma/client in 170ms
13:58:29 db |
13:58:31 api | Listening on http://localhost:8911
13:58:31 api | Watching /Users/isaactait/Desktop/Coding/redwoodblog/api
13:58:31 api |
13:58:31 api | Now serving
13:58:31 api |
13:58:31 api | ► http://localhost:8911/graphql/
13:58:31 web | ℹ ｢wds｣: Project is running at http://localhost:8910/
13:58:31 web | ℹ ｢wds｣: webpack output is served from /
13:58:31 web | ℹ ｢wds｣: Content not from webpack is served from /Users/isaactait/Desktop/Coding/redwoodblog/web
13:58:31 web | ℹ ｢wds｣: 404s will fallback to /index.html
The above error occurred in the <RouterImpl> component:
in RouterImpl (created by LocationProvider)
in LocationProvider (created by Context.Consumer)
in Location (created by Router)
in Router (created by Routes)
in Routes
in ApolloProvider (created by GraphQLProvider)
in GraphQLProvider (created by RedwoodProvider)
in RedwoodProvider
in FatalErrorBoundary
React will try to recreate this component tree from scratch using the error boundary you provided, FatalErrorBoundary. react-dom.development.js:19560
React 18
logCapturedError
logError
payload
getStateFromUpdate
processUpdateQueue
resumeMountClassInstance
updateClassComponent
beginWork
beginWork$1
performUnitOfWork
workLoopSync
performSyncWorkOnRoot
scheduleUpdateOnFiber
updateContainer
legacyRenderSubtreeIntoContainer
unbatchedUpdates
legacyRenderSubtreeIntoContainer
render
js index.js:10
Webpack 7
__webpack_require__
fn
0
__webpack_require__
checkDeferredModules
webpackJsonpCallback
<anonymous>
Ah, helpful indeed. And, unfortunately, this may be a very strange, known Firefox issue you stumbled upon having to do with regex. See below. Could you try a different browser to confirm?
Good to hear! And sorry/not-sorry you had to be a trailblazer (the info is a huge help to us) We’ll* figure something out that hopefully doesn’t require patching an esoteric issue with Firefox that’s apparently been around for a loooong time.
*and by “we” I most definitely mean @peterp who’s been hammering at fixes the past week like a machine
We’ll* figure something out that hopefully doesn’t require patching an esoteric issue with Firefox that’s apparently been around for a loooong time.
