ebd43c7763
This noticeably improves performance in the admin panel, for example
when there are multiple richtext editors on one page (& likely
performance in other areas too, though I mainly tested rich text).
The babel plugin currently only optimizes files with a 'use client'
directive at the top - thus we have to make sure to add use client
wherever possible, even if it's imported by a parent client component.
There's one single component that broke when it was compiled using the
React compiler (it stopped being reactive and failed one of our admin
e2e tests):
150808f608
opting out of it completely fixed that issue
Fixes https://github.com/payloadcms/payload/issues/7366
44 lines
968 B
JSON
44 lines
968 B
JSON
{
|
|
"compilerOptions": {
|
|
"noEmit": true,
|
|
"rootDir": ".",
|
|
"declaration": true,
|
|
"declarationMap": true,
|
|
"target": "esnext",
|
|
"module": "NodeNext",
|
|
"moduleResolution": "NodeNext",
|
|
"allowJs": true,
|
|
"checkJs": false,
|
|
"esModuleInterop": true,
|
|
"forceConsistentCasingInFileNames": true,
|
|
"jsx": "preserve",
|
|
"lib": ["dom", "dom.iterable", "esnext"],
|
|
"resolveJsonModule": true,
|
|
"skipLibCheck": true,
|
|
"sourceMap": true,
|
|
"strict": false,
|
|
"types": ["jest", "node", "@types/jest"],
|
|
"incremental": true,
|
|
"isolatedModules": true,
|
|
"plugins": [
|
|
{
|
|
"name": "next"
|
|
}
|
|
],
|
|
"baseUrl": ".",
|
|
"paths": {
|
|
"@payload-config": ["./_community/config.ts"]
|
|
}
|
|
},
|
|
"exclude": [
|
|
"dist",
|
|
"build",
|
|
"node_modules",
|
|
"eslint.config.js",
|
|
"dist/**/*.js",
|
|
"**/dist/**/*.js"
|
|
],
|
|
"include": ["./**/*.ts", ".next/types/**/*.ts", "setup.js"],
|
|
"references": []
|
|
}
|