chore: replace source-map with trace-mapping #3236
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
antfu
approved these changes
Apr 23, 2023
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Vitest currently uses
[email protected]that takes 789kB.This PR replaces
source-mapwith@jridgewell/trace-mapping.@jridgewell/trace-mappingis 253kB and Vitest already bundles it because@ampproject/remappingdepends on it. So this PR will reduce 789kB.Also
@jridgewell/trace-mappinghas a better performance thansource-map.I tested this PR manually by checking the output of running
pnpm typesintest/typescript.