Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

transformIgnorePatterns option is not used when specified in global config of multi-project setup #5260

Closed
smolyakoff opened this issue Jan 9, 2018 · 4 comments
Labels

Comments

@smolyakoff
Copy link

I'm running jest in a multi-project mode with several projects in subdirectories. The global configuration file in the root directory is as follows

module.exports = {
  rootDir: 'src',
  coverageDirectory: '<rootDir>/../coverage',
  collectCoverageFrom: [
    '**/*.js',
    '!**/index.js',
    '!**/jest.config.js',
  ],
  projects: [
    '<rootDir>/server',
    '<rootDir>/client',
    '<rootDir>/common',
  ],
  transformIgnorePatterns: [
    '/node_modules/(?!lodash-es)',
  ],
};

Project configurations are relatively simple and only differ by testEnvironment (node and jsdom) as for now. I expect jest to use transformIgnorePatterns options for all projects when I run it from the root directory with npm test. But it does work only if I move the mentioned option to the jest configuration in the subdirectory, such as src/client/jest.config.js

Is this an intended behavior or a bug?

@SimenB
Copy link
Member

SimenB commented Jan 9, 2018

I think it's intended (but not wanted), as we have a difference between ProjectConfig and GlobalConfig. See #5176 (comment)

@github-actions
Copy link

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the Stale label Feb 25, 2022
@github-actions
Copy link

This issue was closed because it has been stalled for 7 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants