Jiachi Liu ffc0e54102 Allow server-only in server targets and client-only in client components targets to be available (#55394) ... Users want to use `server-only` to restrict the middleware / app routes / pages api, but now it's failing as we're treating them as different webpack layers, but validating the `server-only` only with server components layers. Here we modify the rules a bit to let everyone can use "server-only" for the bundles that targeting server-side. For next-swc transformer, we introduce the new option `bundleType` which only has `"server" | "client" | "default"` 3 values: * - `server` for server-side targets, like server components, app routes, pages api, middleware * - `client` for client components targets such as client components app pages, or page routes under pages directory. * - `default` for environment like jest, we don't validate module graph with swc, replaced the `disable_checks` introduced [#54891](https://github.com/vercel/next.js/pull/54891). Refactor a bit webpack-config to adapt to the new rules, after that `server-only` will be able to used in the server-side targets conventions like middleware and `pages/api` Fixes #43700 Fixes #54549 Fixes #52833 Closes NEXT-1616 Closes NEXT-1607 Closes NEXT-1385		2023-09-18 12:27:45 +00:00
..
app	Allow server-only in server targets and client-only in client components targets to be available (#55394)	2023-09-18 12:27:45 +00:00
layout.js	Allow server-only in server targets and client-only in client components targets to be available (#55394)	2023-09-18 12:27:45 +00:00