-
Notifications
You must be signed in to change notification settings - Fork 12k
Chunks are not gzipped in production #2340
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
Could be duplicate of #2028? |
@mrgoos I think it's different, after further investigation I noticed that some chunks are gzipped, others not
|
@mwawrusch I think this may be down to how large the chunks are. I know that there is a threshold where compressing the file will actually hurt performance. I would check and see how large the chunks are and see if they are gzipped as they get bigger. |
That seems like a reasonable assumption, as only the smaller files are kept unzipped. |
Closing as dupe of #2028, better to keep gzip discussion there. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
When using lazy loading modules the resulting chunks (like 0.59ea61d3b756000074ac.chunk.js ) are not gzipped.
Yosemite
ng --version
. If there's nothing outputted, please runin a Terminal:
node --version
and paste the result here:angular-cli: 1.0.0-beta.15
node: 6.1.0
os: darwin x64
do on your code? etc.
Create an app with a lazy loaded module. run ng build --prod
more information.
n/a
n/a
The text was updated successfully, but these errors were encountered: