{"id":1013,"date":"2023-05-30T05:00:00","date_gmt":"2023-05-30T12:00:00","guid":{"rendered":"https:\/\/www.angulartraining.com\/daily-newsletter\/?p=1013"},"modified":"2023-05-22T15:07:09","modified_gmt":"2023-05-22T22:07:09","slug":"anti-pattern-not-using-production-builds-to-deploy-production-code","status":"publish","type":"post","link":"https:\/\/www.angulartraining.com\/daily-newsletter\/anti-pattern-not-using-production-builds-to-deploy-production-code\/","title":{"rendered":"Anti-pattern: Not using production builds to deploy production code"},"content":{"rendered":"\n

This is one of the most common mistakes I see with my training\/consulting clients. When deploying code to production, they would use the command: ng build<\/code>.<\/p>\n\n\n\n

Instead, you want to use: ng build --configuration=production<\/code><\/p>\n\n\n\n

Why is that? Because a production build is optimized in several ways<\/strong>:<\/p>\n\n\n\n

    \n
  1. The code gets minified and obfuscated<\/strong>, which means it looks like this when running in a browser:
    <\/li>\n<\/ol>\n\n\n
    \n
    \"\"<\/figure>\n<\/div>\n\n\n

    This code is as lightweight as possible (no tabs, whitespace, new line characters, variables have super short names, etc.) and a lot more challenging to understand (a hacker would have a harder time understanding your code).<\/p>\n\n\n\n

    2. The code gets tree-shaked<\/strong>. Angular removes unused dependencies and dead code and makes your build output as tiny as possible. Size matters on the web: The less code you ship to a browser, the faster it gets downloaded, parsed, and interpreted (which is also why Angular gives us lazy-loading<\/a> capabilities)<\/p>\n\n\n\n

    3. Source maps are not generated<\/strong> in that same spirit of hiding what our source code looks like.<\/p>\n\n\n\n

    4. Angular DevTools are disabled on that code, again for obfuscation and reverse-engineering purposes.<\/p>\n\n\n\n

    <\/p>\n\n\n\n

    If you’re still not convinced after reading all of this, give it a try on your Angular projects. The size of your dist<\/code> folder after a production build should be at least 90 to 95% smaller compared to a regular build, which is massive.<\/p>\n","protected":false},"excerpt":{"rendered":"

    This is one of the most common mistakes I see with my training\/consulting clients. When deploying code to production, they would use the command: ng build. Instead, you want to use: ng build –configuration=production Why is that? Because a production build is optimized in several ways: This code is as lightweight as possible (no tabs, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,28,30,20,17],"tags":[],"class_list":["post-1013","post","type-post","status-publish","format-standard","hentry","category-angular","category-anti-patterns","category-cli","category-performance","category-tools"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t