Await Params: Error on Build
Unanswered
West African Crocodile posted this in #help-forum
West African CrocodileOP
I have a functional implementation in development with params, but when I build it, I get an error. What could it be?
20 Replies
@West African Crocodile I have a functional implementation in development with params, but when I build it, I get an error. What could it be?
can you put the page inside a
loading.tsx
and see if it works then?West African CrocodileOP
Like this? The error persists
@West African Crocodile Like this? The error persists
yes, can you show the content of loading.tsx?
West African CrocodileOP
It is in the right panel. The content is:
export default function Loading() {
return <div>Loading</div>;
}
@West African Crocodile It is in the right panel. The content is: export default function Loading() {
return <div>Loading</div>;
}
the canary version of nextjs can have bugs and dynamicIO might have bugs as well. Can you reproduce the error inside a github library or [codesandbox](https://codesandbox.io/)? Like that we can test around while you are offline 🙂
West African Crocodile
I think FlashcardsPage isn't async function.
try delete async!
try delete async!
West African CrocodileOP
The error persists. @West African Crocodile, I'm recreating the error on CodeSandbox, give me a moment.
West African Crocodile
I am sorry but this is your question.
https://nextjs.org/docs/messages/next-prerender-missing-suspense
https://nextjs.org/docs/messages/next-prerender-missing-suspense
good luck
@West African Crocodile I am sorry but this is your question.
https://nextjs.org/docs/messages/next-prerender-missing-suspense
I guess he already knows his error, as the error is printed inside the console. He working on a codesandbox right now that reproduces the error
West African Crocodile
oh, got it
West African CrocodileOP
I cannot reproduce the error, I will be checking if any dependency is the culprit.
@West African Crocodile I cannot reproduce the error, I will be checking if any dependency is the culprit.
Hmm, yea. Try to delete the .next folder and try again. If that doesn’t help, reinstall the node_modules (delete folder & npm install). If that doesn’t work, check your local dependencies. Maybe there is something (try with clean install for example)
West African CrocodileOP
@B33fb0n3 Could you share your username with me?
Sure, it’s B33fb0n3. Make sure it’s a public Repro (you can exclude exclusive details if needed) so others can help as well
West African CrocodileOP
@B33fb0n3 Sure, it’s B33fb0n3. Make sure it’s a public Repro (you can exclude exclusive details if needed) so others can help as well
West African CrocodileOP
It is a private project, and I was unable to replicate the error from scratch. If someone wants to review it, they can pass me their username... Or I think this link can help: https://codesandbox.io/invite/y95yrjwsyxc9trjv
@West African Crocodile Click to see attachment
don't share your secrets
West African CrocodileOP
They are only for development, there is no issue
@West African Crocodile It is a private project, and I was unable to replicate the error from scratch. If someone wants to review it, they can pass me their username... Or I think this link can help: https://codesandbox.io/invite/y95yrjwsyxc9trjv
West African CrocodileOP
Note: MongoDB can be used locally (CodeSandbox) with Docker to avoid build errors, ex: docker run --name my-mongo-db -p 27017:27017 -d mongo:latest