gzip not getting created on ng build --prod #5330

Activity

1. RicardoVaranda commented on Mar 9, 2017

   

   RicardoVaranda

   on Mar 9, 2017

   Contributor

   More actions

   Dupe of #5272 , This is outside of the scope of cli, you should be configuring the gzip settings in the server which is hosting your files like apache/nginx etc.
2. filipesilva commented on Mar 9, 2017

   

   filipesilva

   on Mar 9, 2017

   Contributor

   More actions

   Closing as dupe, thanks @RicardoVaranda!
3. filipesilva

   closed this as completedon Mar 9, 2017
4. kaynz commented on Apr 20, 2017

   

   kaynz

   on Apr 20, 2017

   More actions

   @RicardoVaranda @filipesilva
   Most webservers (like nginx) are able to serve static files, e.g. if you have a vendor.bundle.js.gz next to your vendor.bundle.js, it'll serve the already compressed .gz file instead of using cpu to compress it again.

   Therefore I think it would be great if ng build --prod would create gzipped files directly.

   👍React with 👍52Reacted by Ravinder Payal, Rajesh, Oduntan Oluwatobiloba Stephen, Vladimir Pavlenko, William Grasel, zuosanmu, ooptsd, Todd Werelius, Vasco Correia, Cyril and 42 more
5. vcorr commented on May 24, 2017

   

   vcorr

   on May 24, 2017

   More actions

   I agree, I understood it did create gz-files at some point, but this functionality was removed?
6. John0x commented on Jun 12, 2017

   

   John0x

   on Jun 12, 2017

   More actions

   I don't see a reasony, why the cli should not support gzipping. Why has it been removed?
7. jgodi commented on Jun 12, 2017

   

   jgodi

   on Jun 12, 2017

   More actions

   You can see the answer here: #4618 (comment)
8. drjackson commented on Jul 12, 2017

   

   drjackson

   on Jul 12, 2017

   More actions

   I wish there was still at least an option for gzip.
9. zac1st1k commented on Aug 3, 2017

   

   zac1st1k

   on Aug 3, 2017

   More actions

   in fact, webpack-dev-server supports gzip. https://github.com/webpack/webpack-dev-server/tree/master/examples/compression Anguar CLI can pass the parameter down to the server. It is really good for estimating the production performance on a local environment.

   👍React with 👍8Reacted by Nektarios Konstantinidis, Mr. Happiness, ashishkhanna15, Michał Michalczuk, Huan Li, gfranco93, Damodharan J and tdev

   😕React with 😕4Reacted by km, CAspeling, tjvanderende and Alexej Strelzow
10. tan9 commented on Oct 5, 2018

    

    tan9

    on Oct 5, 2018

    More actions

    I ended up using "gzip-all":https://www.npmjs.com/package/gzip-all in my package.json:

    {
        "...": "...",
        "scripts": {
            "...": "...",
            "build-prod": "ng build --prod && gzip-all \"dist/anti-fraud/*.*\"",
            "...": "...",
        },
        "...": "...",
    }

    👍React with 👍4Reacted by Hadrien TOMA, Gordon, tkarpenko and Khanh Ngo
11. rynop commented on Oct 9, 2018

    

    rynop

    on Oct 9, 2018

    Last edited by rynop

    More actions

    I think the trend is for SPA to be hosted in a static object store like S3. While a CDN can be put in front to gzip on the fly, IMO it is a waste.

    My vote would be to put it back into ng build as an optional param, given the number of people that need the use case and the trend mentioned above.

    For those looking for a workaround:

    package.json:

    ...
        "build:prod": "ng build --prod --build-optimizer --delete-output-path --aot",
        "deploy:prod": "yarn run build:prod && gzip-all \"dist/my-webapp/*.{css,js,html}\" && bin/deploy.sh www.me.io",
    ...
    

    bin/deploy.sh:

    #!/bin/bash
    
    APP_NAME=my-webapp
    if [[ "$1" != "" ]]; then
        S3BUCKETNAME="$1"
    else
        echo ERROR: Failed to supply S3 bucket name
        exit 1
    fi
    
    for old in dist/${APP_NAME}/*.gz; do mv $old ${old%%.gz*}; done
    aws s3 sync dist/${APP_NAME} s3://${S3BUCKETNAME} --metadata-directive REPLACE --cache-control max-age=31536000,public --acl public-read --exclude "index.html" --exclude "*.css" --exclude "*.js" || { echo 'ERROR: s3 sync failed' ; exit 1; }
    aws s3 sync dist/${APP_NAME} s3://${S3BUCKETNAME} --metadata-directive REPLACE --cache-control max-age=31536000,public --acl public-read --exclude "*" --include "*.css" --include "*.js" --content-encoding gzip || { echo 'ERROR: s3 js/css sync failed' ; exit 1; }
    aws s3 cp dist/${APP_NAME}/index.html s3://${S3BUCKETNAME}/index.html --metadata-directive REPLACE --cache-control max-age=0,no-cache,no-store,must-revalidate --content-type text/html --acl public-read --content-encoding gzip || { echo 'ERROR: s3 cp index failed' ; exit 1; }
    
    
    

    👍React with 👍6Reacted by Markus Dresch, tdev, Sandor, Josh Tune, Ahn and Edoardo Luppi
12. tdev9 commented on Jan 21, 2019

    

    tdev9

    on Jan 21, 2019

    More actions

    Optional params to generate gzip would be very helpful to don't have to use workarounds.

    👍React with 👍11Reacted by Konstantin Nosov, Nick Partridge, Mahdi Haji Abdolvahab, lucanLepus, Sandor, Lucas Tétreault, Egor, Ahn, Fedor Shchudlo, Edoardo Luppi and 1 more
13. angular-automatic-lock-bot commented on Sep 9, 2019

    

    angular-automatic-lock-botBot

    on Sep 9, 2019

    More actions

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    _{This action has been performed automatically by a bot.}
14. angular-automatic-lock-bot

    locked and limited conversation to collaborators on Sep 9, 2019