Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Optimize bundle sizes #6

Open
appsforartists opened this issue Jul 7, 2016 · 4 comments
Open

Optimize bundle sizes #6

appsforartists opened this issue Jul 7, 2016 · 4 comments
Labels
Internal cleanup Needs research

Comments

@appsforartists
Copy link
Member

  • Make examples depend on dist (rather than bundling it)
  • Figure out why Webpack spits out such big bundles and how to make them tiny.

Loosely related to #3.
@jverkoey jverkoey modified the milestones: Runtime v1, Runtime v1.0.0, Distribution strategy Jul 11, 2016
@appsforartists appsforartists mentioned this issue Jul 26, 2016
Closed
appsforartists added a commit that referenced this issue Jul 27, 2016
@appsforartists
[_fixed] source maps
f5015db 
Summary:
Useless source maps were previously being emitted both by `npm start` and `npm run build`.  Now, correct source maps are emitted inline during development and in separate files by `npm run build`.  This both makes development easier and helps make the bundle size reasonable.

Progress towards #6

Reviewers: O2 Material Motion

Tags: #material_motion

Differential Revision: http://codereview.cc/D1358
@appsforartists
Copy link
Member Author

Also explore if Closure Compiler or TypeScript do a better job than Webpack + Uglify for bundling.
@appsforartists
Copy link
Member Author

My current plan is to test if using rxjs in TypeScript tree-shakes as effectively as using rxjs-es and the :: operator does now. If so, I'll likely migrate from rxjs-es and Flow to rxjs and TypeScript to make the toolchain more congruent with what's in use internally (and to avoid having to write transforms to convert Flow annotations to Closure type annotations). We're not getting much use out of Flow now, because :: breaks its parser.

Will likely spend the next few weeks prototyping the Circles interaction and then start exploring this.
appsforartists added a commit that referenced this issue Aug 15, 2016
@appsforartists
[_added] WebpackDashboard
578b7da 
May be useful for visualizing Webpack builds and relative [file-size impact](#6) for dependencies.  Current outstanding issues:

- [Makes dev server startup 3x slower](FormidableLabs/webpack-dashboard#18)
- [Breaks control-C to kill both Node and Python](FormidableLabs/webpack-dashboard#20)
@appsforartists
Copy link
Member Author

There's also the new Webpack Closure plugin that we can experiment with.
@appsforartists appsforartists mentioned this issue Aug 21, 2016
Open
@appsforartists
Copy link
Member Author

The Cost of Small Modules is one more point in the Closure bucket.
@jverkoey jverkoey removed this from the Distribution strategy milestone Dec 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Internal cleanup Needs research
2 participants
@jverkoey @appsforartists