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
Cache source map results #104
Comments
this seems like it would be a reasonable improvement, I'd be curious to see a benchmark that indicates it's worth doing though, as it introduces some complexity. For instance, annoying edge-cases like colliding source map names. |
also how it'd behave if Jest (or something else) is running in watch mode, how would we avoid stale caches? |
You can allow the calling library to provide the cache, which would be fresh for each test run. |
When repeatedly calling this library, it looks up the source maps each time. It would be more efficient if the source map information is cached between invocations.
I can work on a PR for that if this is something you are ok with adding.
The text was updated successfully, but these errors were encountered: