-
Notifications
You must be signed in to change notification settings - Fork 71
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
Use @benthemonkey source-map fork #100
Conversation
We need published package... |
Yeah, repo can be deleted. |
Sure I'll do this today. |
Let's change it in |
@benthemonkey thanks for the rapid feedback! @alexander-akait it's done |
I think it's ready, but let's wait for benthemonkey/source-map#1. I will try to polish and release it this weekend. |
@7rulnik thanks for fixing it |
@7rulnik feel free to ping me when it will be ready |
@alexander-akait I finished optimizations and moved to https://www.npmjs.com/package/source-map-js For more info see 7rulnik/source-map-js#2 As a result, parsing became 4x faster and serialization 30% faster |
@benthemonkey made a
source-map
fork and backported mozilla/source-map#308 to js implementation.Patch diff: mozilla/source-map@0.6.1...benthemonkey:patch-0.6.1
Sources of the idea:
mozilla/source-map#370
zulip/zulip#16545
Related to #34
I tried to run the benchmark in webpack repo but got jest error
Your test suite must contain at least one test
. Also, there is some problem with Travis, but tests passed on my machine.