Skip to content

Commit b4ccef3

Browse files
use nolyfill to remove some polyfills (#31468)
We don't need to have polyfills down to Node v4. Some of our deps have polyfills, and don't utilize the built-in implementation if available. While this does decrease our package graph, I haven't been able to notice any decrease/increase in page load times, although that could likely be just because it's already pretty fast. Nolyfill is https://github.com/SukkaW/nolyfill updates to files generated with: ```shell npx nolyfill install npm update ``` Before this is/isn't merged, I'd be appreciative/thankful for other's insights. Edit: This isn't due to a specific individual. I am generally supportive of them and their dedication to backward compatibility. This PR is due to not needing those imports for our minimum requirements. Please don't take this PR as commentary on anyone's character. --------- Co-authored-by: silverwind <[email protected]>
1 parent c0b5a84 commit b4ccef3

File tree

3 files changed

+346
-1615
lines changed

3 files changed

+346
-1615
lines changed

Diff for: Makefile

+2
Original file line numberDiff line numberDiff line change
@@ -887,6 +887,8 @@ update-js: node-check | node_modules
887887
npx updates -u -f package.json
888888
rm -rf node_modules package-lock.json
889889
npm install --package-lock
890+
npx nolyfill install
891+
npm install --package-lock
890892
@touch node_modules
891893

892894
.PHONY: update-py

0 commit comments

Comments
 (0)