Skip to content
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.

Investigate the performance cost parsing the bundle #2937

Closed
jasonLaster opened this issue May 17, 2017 · 1 comment
Closed

Investigate the performance cost parsing the bundle #2937

jasonLaster opened this issue May 17, 2017 · 1 comment
Labels
👷‍♀️ performance infrastructure

Comments

@jasonLaster
Copy link
Contributor

jasonLaster commented May 17, 2017 •
edited

The debugger's primary bundle is 50K lines of code. We should measure the cost of parsing it and if it is significant, then trim some of the bundle fat.

We should consider vendoring lodash and babel as well
@jasonLaster jasonLaster added this to the August 15th milestone Jul 31, 2017
@jasonLaster
Copy link
Contributor Author

duplicate of #3189

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
👷‍♀️ performance infrastructure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jasonLaster