Normal Build
Creating a normal build in front-end Application is useful for deploying the application to a web server or a content delivery network (CDN) where it can be accessed by users through a web browser.
A normal build in Angular creates a set of optimized static files, including JavaScript, HTML, and CSS, that can be served from a web server. These files are optimized for performance and include features like tree-shaking, ahead-of-time (AOT) compilation, and minification, which can reduce the size of the application and improve its load time.
There are several benefits to using a normal build in front-end Application:
Performance: Normal builds can be optimized for performance using features like tree-shaking, AOT compilation, and minification. This can help to reduce the size of the application and improve its load time.
Compatibility: Normal builds can be deployed to any web server or CDN that supports static file hosting, making it easy to distribute your application to a wide range of devices and platforms.
Security: Normal builds can be served over HTTPS, providing secure communication between the server and the browser.
Maintainability: Normal builds can be easily updated and deployed, allowing you to quickly make changes and improvements to your application.
In summary, creating a normal build in Angular is useful for deploying your application to a web server or CDN, and can provide benefits like improved performance, compatibility, security, and maintainability.
SSR Build
A front-end JavaScript framework that runs in the browser. When you first load an Angular application, the entire application is downloaded to the browser, including all the JavaScript, HTML, and CSS files. This can result in slow load times and a poor user experience, especially on slower internet connections or on mobile devices.
Server-side rendering (SSR) can help to improve the performance of applications by pre-rendering the initial HTML on the server and sending it to the browser. This means that the user can see content more quickly and the application feels faster, even on slower connections.
There are several benefits to using SSR with Angular:
Faster load times: By rendering the initial HTML on the server, the user can see content more quickly, which can improve the user experience.
Better SEO: Search engines can crawl and index server-rendered pages more easily, which can improve the visibility of your application in search results.
Improved performance: By reducing the amount of work the browser needs to do to render the page, you can improve the performance of your application and reduce the load on the user's device.
Accessibility: Server-side rendering can make your application more accessible to users who rely on screen readers or other assistive technologies.
In summary, creating an SSR build in Angular can help to improve the performance and user experience of your application, and can make it more accessible and SEO-friendly.
Top comments (0)