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
When I use the included resolver, my (few) tests take more than 7 seconds, taking a while to start running. When I use the default resolver, the tests take little over 1 second. That's a massive difference and has a real impact on how easy it is to develop with tests.
The comment says:
uses a webpack style resolver, the default one has many issues.
I'd be interested in seeing what I'm paying for in some more detail. And maybe there's a way to configure this resolver to be faster? (I tried upgrading enhanced-resolver to 5.9.3, the latest release, but it made no difference)
The text was updated successfully, but these errors were encountered:
It's also interesting to speculate why enhanced-resolver is so much slower. Is this because it does more work per module, or because it actually finds many more modules and needs to disregard them?
When I use the included resolver, my (few) tests take more than 7 seconds, taking a while to start running. When I use the default resolver, the tests take little over 1 second. That's a massive difference and has a real impact on how easy it is to develop with tests.
The comment says:
uses a webpack style resolver, the default one has many issues.
It's using https://www.npmjs.com/package/enhanced-resolve-jest which in turn uses https://github.com/webpack/enhanced-resolve
I'd be interested in seeing what I'm paying for in some more detail. And maybe there's a way to configure this resolver to be faster? (I tried upgrading
enhanced-resolver
to 5.9.3, the latest release, but it made no difference)The text was updated successfully, but these errors were encountered: