Bug 508336 - Escope library is too big
Summary: Escope library is too big
Status: RESOLVED FIXED
Alias: None
Product: Orion (Archived)
Classification: ECD
Component: JS Tools (show other bugs)
Version: 13.0   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 13.0   Edit
Assignee: Michael Rennie CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2016-11-28 16:39 EST by Michael Rennie CLA
Modified: 2016-11-29 10:43 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rennie CLA 2016-11-28 16:39:59 EST 
After all the trouble we had updating to EScope 3.6 (because it is fully es6-ified), I was investigating a fix for bug 506993 only to find that there is no way to debug through escope (since the webpack build also minifies it).

I had a look at rollup (https://github.com/rollup/rollup) and successfully built escope (without built-in dependencies) and it is only a fraction of the size webpack can build it to (~2000LOC vs ~5400LOC).

I'll commit this version of escope since it uses much, much less memory and loads much faster.

I'll also commit the rollup config file I used and write a short readme for others to build escope easily.
Comment 1 Michael Rennie CLA 2016-11-28 17:30:01 EST 
Pushed the new built version + readme + config file to:

http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=a94b944edd3bede1ac323b6eac6f948b181477fa.

All tests pass, but I'll wait for a build to test to make sure everything is ok before closing.
Comment 2 Michael Rennie CLA 2016-11-29 10:43:52 EST 
Its been in the last few builds and working fine. Closing.