Closed nikolay-borzov closed 4 years ago
I thought about the performance test but haven't figure out how to implement it yet. Should it be just measuring big source map processing time (outside main code) or adding measures to several places in code?
I think running source-map-explorer --json
with a single large JS file (large enough to have shown the regression in the bug) would be sufficient. We could run that either as part of CI or as part of the release process.
158 has shown that some unobvious changes could reduce performance greatly.
We should add a simple performance test to track such cases.