-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Try new build #4883
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
base: main
Are you sure you want to change the base?
Try new build #4883
Conversation
6bc7965
to
8b9e986
Compare
📊 Tachometer Benchmark ResultsSummaryduration
usedJSHeapSize
Resultscreate10kduration
usedJSHeapSize
filter-listduration
usedJSHeapSize
hydrate1kduration
usedJSHeapSize
many-updatesduration
usedJSHeapSize
replace1kduration
usedJSHeapSize
run-warmup-0
run-warmup-1
run-warmup-2
run-warmup-3
run-warmup-4
run-final
text-updateduration
usedJSHeapSize
tododuration
usedJSHeapSize
update10th1kduration
usedJSHeapSize
|
Size Change: -16.1 kB (-33.86%) 🎉 Total Size: 31.4 kB
|
ffd5899
to
132d9c2
Compare
dc82203
to
efc60d9
Compare
020e813
to
623ddd5
Compare
623ddd5
to
d63a37f
Compare
2f77355
to
33128c8
Compare
I was under the impression that the ES2020 setting was just a temporary thing whilst you were working on this, is that not the case? I feel that's a bit too new to place our floor at, and I'm not sure it's necessary -- do we/the transpiler even use anything that new? ES2017 or so, IMO, should be as new as it gets if absolutely required. Moving past ES5 also likely calls for investigation into ES6 classes, they'll certainly be smaller but perf could go either way. Not necessarily related to this PR of course, just opens up a few new options that could be good for us. |
General changes
TODO
compat.mjs