af9837de44
This adds a new `analyze` step to our CI that analyzes the bundle size for our `payload`, `@payloadcms/ui`, `@payloadcms/next` and `@payloadcms/richtext-lexical` packages. It does so using a new `build:bundle-for-analysis` script that packages can add if the normal build step does not output an esbuild-bundled version suitable for analyzing. For example, `ui` already runs esbuild, but we run it again using `build:bundle-for-analysis` because we do not want to split the bundle. --- - To see the specific tasks where the Asana app for GitHub is being used, see below: - https://app.asana.com/0/0/1210692087147570
29 lines
524 B
JSON
29 lines
524 B
JSON
{
|
|
"$schema": "https://turbo.build/schema.json",
|
|
"tasks": {
|
|
"clean": {
|
|
"cache": false,
|
|
"dependsOn": ["^clean"]
|
|
},
|
|
"build": {
|
|
"cache": true,
|
|
"dependsOn": ["^build"],
|
|
"outputs": ["./dist/**"]
|
|
},
|
|
"build:bundle-for-analysis": {
|
|
"cache": true,
|
|
"dependsOn": ["^build:bundle-for-analysis"],
|
|
"outputs": ["./esbuild/**"]
|
|
},
|
|
"dev": {
|
|
"cache": false
|
|
},
|
|
"lint": {
|
|
"cache": false
|
|
},
|
|
"lint:fix": {
|
|
"cache": false
|
|
}
|
|
}
|
|
}
|