You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For large applications, it could be useful to be able to do a mix between TS jest transformation and esbuild transformation in order to optimize the performance which are kind of slow on a CI for around 800spec files. (3 agents around 10min per agent)
By allowing the loader to be overridden depending on the file type, it would let us do advanced customization in order to boost the performance of the tests execution. (for example, all the mock files, all the fixtures file, all the spec files can be transformed with esbuild... and any files without decorators because for decorators it would be harder to implement)
We plan to switch to @swc instead of esbuild since it's a recommended one to replace Babel and we want to support transform native async/await to Promise for target which is later than ES2016
We would use transformerOptions instead of globals, e.g
transform: {
'^.+\\.(ts|js|html|svg)$': ['jest-preset-angular', {
processWithEsbuild: [
'**/src/testing/mocks/*.ts',
'**/src/common/**/*.ts',
'**/src/**/*.spec.ts'
] // `processWithEsbuild` probably should be renamed to something else
}]
}
🚀 Feature Proposal
At the moment, in https://github.com/thymikee/jest-preset-angular/blob/main/src/ng-jest-transformer.ts, esbuild won't be able to process any typescript file since the loader is hardcoded to JS.
For large applications, it could be useful to be able to do a mix between TS jest transformation and esbuild transformation in order to optimize the performance which are kind of slow on a CI for around 800spec files. (3 agents around 10min per agent)
By allowing the loader to be overridden depending on the file type, it would let us do advanced customization in order to boost the performance of the tests execution. (for example, all the mock files, all the fixtures file, all the spec files can be transformed with esbuild... and any files without decorators because for decorators it would be harder to implement)
As a very simple solution,
This way, it would not produce any errors while trying to benefit from esbuild for some TS files.
What are your thought @thymikee ?
Thank you :)
Motivation
Tweaking the configuration in order to improve the performance to run the tests on CI agents which are usually slower.
Example
Using
to have all the files not containing any decorators transformed by esbuild which is faster.
The text was updated successfully, but these errors were encountered: