rsnext/test/e2e/app-dir/rsc-basic
Jiachi Liu afe4f2fe13
Fix the runtime for rsc layer (#65850)
### What

Fix a bug introduced in #65694 , use app-page runtime for app router
layers

### Why

This is basically reverted the route context picking up logic we had
before.

During the test we found the error thrown
> Module not found: shared-runtime module router-context cannot be used
in rsc layer

Which is caused by a `next/router` imports in rsc page. Decided to
revert to what it was before as the most safe way to load share module
contexts.

It's caused by `next-contentlayer` usage that they're using
`next/router` in server component MDX, but we cannot lint error that
from node_modules. (We actually can, but disabled that due to various
mis-usage of server/client hooks we had before)
2024-05-16 18:27:35 +02:00
..
app Fix the runtime for rsc layer (#65850) 2024-05-16 18:27:35 +02:00
components Drop object config export support for app dir (#48489) 2023-04-17 20:02:32 +00:00
lib Handle dynamic css-in-js styles under suspense (#42293) 2022-11-02 14:18:08 +01:00
pages Fix the runtime for rsc layer (#65850) 2024-05-16 18:27:35 +02:00
public Migrate rsc integration tests to e2e tests (#38460) 2022-07-09 14:02:30 +02:00
next.config.js Promote and rename server bundling options serverComponentsExternalPackages and bundlePagesExternals (#65421) 2024-05-07 11:19:35 -06:00
rsc-basic.test.ts Fix the runtime for rsc layer (#65850) 2024-05-16 18:27:35 +02:00