Skip to content
This repository has been archived by the owner on Dec 19, 2017. It is now read-only.

Investigate minification of js/css/html during deployment #181

Open
jakemac53 opened this issue Jan 9, 2015 · 5 comments
Open

Investigate minification of js/css/html during deployment #181

jakemac53 opened this issue Jan 9, 2015 · 5 comments

Comments

@jakemac53
Copy link
Contributor

Mangling names would be hard due to the js-interop, but we should be able to save a lot of space by just removing comments and collapsing whitespace. We should do this for html/css/js

@jakemac53
Copy link
Contributor Author

Whatever solution we use here should also be applied to https://github.com/dart-lang/paper-elements

@Andersmholmgren
Copy link

Be nice if there is any way to apply tree shaking to the elements. Remove unused elements etc

@jakemac53
Copy link
Contributor Author

I agree, but we can't really do that until we have global transformers (see http://dartbug.com/17306). The application is the only thing that knows what it could delete, but it can't delete files in this package.

@zoechi
Copy link

zoechi commented Jan 14, 2015

Shouldn't it be possible to just run vulcanize or some other JavaScript minification after pub build to achive this?

@jakemac53
Copy link
Contributor Author

Yes, but it would be nice if we could integrate that into the transformation process, eliminating any extra steps and standardizing how its done.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

3 participants