Jiachi Liu
Jiachi Liu
* Use eager `import()` to load page/layout to avoid esm module resolution error, eager is to make sure all the sub resources like css are also included * Fix layer...
## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature...
x-ref: #42293
When using `next/dynamic` in server components to load a client component with named export, we shouldn't dot into the prop name since client component reference as it's already a valid...
Make sure the version is always display on error overlay if possible, to avoid that we saw it's "update to date" in screenshot but still no idea about the version...
### What The `arg` in the worker callback is alwasy `any`, when we access the page path the argument could be in different form as the arg types are different....
### What Switch bundler to bunchee and refine the configurations in packages.json. This helps the types resolution become more compatible among node10, node16 composing with CJS/ESM resolutions. And you dont...
### What Adding the `layer` info to the build error message ```diff Attempted import error: 'useState' is not exported from 'react' (imported as 'useState'). Import trace for requested module: ./node_modules/react-client-pkg/client.js...
* Simplify the export and mark swr context with "use client" * Upgrade bundler