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
30 lines
643 B
JavaScript
30 lines
643 B
JavaScript
import { rootEslintConfig, rootParserOptions } from '../../eslint.config.js'
|
|
|
|
/** @typedef {import('eslint').Linter.Config} Config */
|
|
|
|
/** @type {Config[]} */
|
|
export const index = [
|
|
...rootEslintConfig,
|
|
{
|
|
settings: {
|
|
next: {
|
|
rootDir: '../../app/',
|
|
},
|
|
},
|
|
},
|
|
{
|
|
languageOptions: {
|
|
parserOptions: {
|
|
...rootParserOptions,
|
|
tsconfigRootDir: import.meta.dirname,
|
|
projectService: {
|
|
// See comment in packages/eslint-config/index.mjs
|
|
allowDefaultProject: ['bundleScss.js', 'bundle.js', 'babel.config.cjs'],
|
|
},
|
|
},
|
|
},
|
|
},
|
|
]
|
|
|
|
export default index
|