rsnext/test/e2e/app-dir/dynamic
Jiachi Liu 1a04d94aae
Remove extra suspense boundary for default next/dynamic (#67014)
### What

Reland #64716 

Removing the Suspense boundary on top of `next/dynamic` by default, make
it as `React.lazy` component with preloading CSS feature.

* Remove `suspense` option in `next/dynamic` since it's already
deprecated for a while
* Remove the default loading in app router implmentation of
`next/dynamic`

### Why

Extra Suspense boundary is causing extra useless rendering. For SSR, it
shouldn't render `loading` by default

Related: #64060
Related: #64687
Closes
[NEXT-3074](https://linear.app/vercel/issue/NEXT-3074/app-router-content-flickering-with-reactcreatecontext-and-nextdynamic)

This is sort of a breaking change, since removing the Suspense boundary
on top of `next/dynamic` by default. If there's error happening in side
the dynamic component you need to wrap an extra Suspense boundary on top
of it
2024-06-25 20:40:09 +02:00
..
app Remove extra suspense boundary for default next/dynamic (#67014) 2024-06-25 20:40:09 +02:00
pages/legacy Separate next/dynamic implementation for app and pages (#45565) 2023-02-04 01:45:35 +00:00
ui Fix dynamic no ssr with babel transform (#45091) 2023-01-23 13:39:47 -08:00
dynamic.test.ts Remove extra suspense boundary for default next/dynamic (#67014) 2024-06-25 20:40:09 +02:00
next.config.js Remove experimental config from create-next-app (#49241) 2023-05-05 00:22:28 -07:00