mirror of
https://github.com/twentyhq/twenty.git
synced 2024-12-12 11:20:40 +03:00
514417245a
We were missing `JsDom` dependencies in the package.json generated by nx while running `twenty-server`: `yarn nx build:packageJson` Detailed explanation: - we are currently using nx paradigm which is to put dependencies of all projets at root, which enables global package migrations for the whole monorepo - for production containers, we only want specific project dependency to be added. This is done by running `yarn nx build:packageJson` on `twenty-server`. Nx is statically analyzing twenty-server dependencies and generating a tailored package.json that production containers can later use. - However, `nx` static analysis is not flawless and is missing some packages. We are going to stop using it as the value is not there yet but the burden for developers is high. The guideline is to put back project dependencies into specific package `package.json` - Therefore, I'm adding `jsdom` to twenty-server `package.json`
31 lines
626 B
JavaScript
31 lines
626 B
JavaScript
const globalCoverage = {
|
|
statements: 60,
|
|
lines: 60,
|
|
functions: 60,
|
|
exclude: ['src/generated/**/*'],
|
|
};
|
|
|
|
const modulesCoverage = {
|
|
statements: 70,
|
|
lines: 70,
|
|
functions: 65,
|
|
include: ['src/modules/**/*'],
|
|
exclude: ['src/**/*.ts'],
|
|
};
|
|
|
|
const pagesCoverage = {
|
|
statements: 55,
|
|
lines: 55,
|
|
functions: 45,
|
|
exclude: ['src/generated/**/*', 'src/modules/**/*', 'src/**/*.ts'],
|
|
};
|
|
|
|
const storybookStoriesFolders = process.env.STORYBOOK_SCOPE;
|
|
|
|
module.exports =
|
|
storybookStoriesFolders === 'pages'
|
|
? pagesCoverage
|
|
: storybookStoriesFolders === 'modules'
|
|
? modulesCoverage
|
|
: globalCoverage;
|