You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't see the need to block rendering in development, as these paths are not statically generated anyway. So it would be nice if Next did this if (process.env.NODE_ENV !== 'production') skip automatically.
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
The text was updated successfully, but these errors were encountered:
rijk
added
the
bug
Issue was opened via the bug report template.
label
Jan 6, 2023
Follow-up to #46906 this ensures
we revalidate `generateStaticParams`/`getStaticPaths` in the background
in development so that we aren't blocking refreshes an much
un-necessarily if the paths cache is already populated.
Fixes: #44646Fixes: #38757
x-ref:
#17977 (comment)
x-ref: #20076
x-ref: #14378
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
Verify canary release
Provide environment information
Which area(s) of Next.js are affected? (leave empty if unsure)
App directory (appDir: true), Data fetching (gS(S)P, getInitialProps)
Link to the code that reproduces this issue
To Reproduce
Have a tree with quite some static paths. For me it is:
So in total 1280 paths.
Describe the Bug
Loading pages (especially from level 2) is excruciatingly slow in development:
I had to work around it by doing:
Then it's:
Expected Behavior
I don't see the need to block rendering in development, as these paths are not statically generated anyway. So it would be nice if Next did this
if (process.env.NODE_ENV !== 'production') skip
automatically.Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
The text was updated successfully, but these errors were encountered: