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

[Bug]: Slow startup on larger projects #1168

Closed
cgrantnz opened this issue Nov 15, 2021 · 2 comments · Fixed by #1169
Closed

[Bug]: Slow startup on larger projects #1168

cgrantnz opened this issue Nov 15, 2021 · 2 comments · Fixed by #1169

Comments

@cgrantnz
Copy link

Version

11.0.0-rc.3

Steps to reproduce

  1. Clone https://github.com/callumelgrant/jest-preset-angular
  2. Run yarn test in the Angular 13 example.

Expected behavior

It would be nice to see a test run time more similar to the earlier versions of jest-preset-angular.

Actual behavior

Running yarn test takes ~65 seconds from a cold cache after adding lodash-es. Is there any way to reduce this?

Additional context

After adding more packages to the solution the transformation time seems to increase considerably - in our yarn workspace running yarn test on a cold cache takes 20 minutes before starting to run tests.

Environment

System:
    OS: Windows 10 10.0.19042
    CPU: (16) x64 AMD Ryzen 7 PRO 4750U with Radeon Graphics
  Binaries:
    Node: 16.13.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.15 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 8.1.0 - C:\Program Files\nodejs\npm.CMD
  npmPackages:
    jest: ^27.3.1 => 27.3.1
@ahnpnl
Copy link
Collaborator

ahnpnl commented Nov 15, 2021

Currently workaround is:

it is a performance issue which exists for a long time, not specific to 11.0.0-rc.3

@ahnpnl
Copy link
Collaborator

ahnpnl commented Nov 15, 2021

The provided solution will solve partially the problem only as we rely on ts-jest about performance with type checking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants