-
-
Notifications
You must be signed in to change notification settings - Fork 199
Possible Build Optimizations #249
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.
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
Comments
Hey Ryan, Maybe we should wait for Webpack 4 (see #250) before starting to work on that, they seem to have included some of the optimizations described in this post in their default settings (such as the UglifyJS parallelization). Also, some related issues:
|
I think that's probably wise :) |
Have somebody tried https://github.com/webpack-contrib/thread-loader? I do not even know how to add it to babel loaders list. It is not in the options. |
I also do not understand how to try https://github.com/trivago/parallel-webpack with Encore. |
This is a hariy hack, but this got it working for typescript files. Better yet would be to request a feature to allow pre-pending loaders.
I made a feature request to allow pre-pending loaders: #852 |
I want to second supporting Dllplugin. |
Thank you for this issue. |
Totally just dropping this here until I have some more time to look at it, but Slack had a nice summary of build optimizations: https://slack.engineering/keep-webpack-fast-a-field-guide-for-better-build-performance-f56a5995e8f1
It may be possible that we can package some of these automatically for users :)
The text was updated successfully, but these errors were encountered: