{"id":1790,"date":"2023-11-17T05:00:00","date_gmt":"2023-11-17T13:00:00","guid":{"rendered":"https:\/\/www.angulartraining.com\/daily-newsletter\/?p=1790"},"modified":"2023-11-16T18:32:23","modified_gmt":"2023-11-17T02:32:23","slug":"angular-17-signals-server-side-rendering-and-standalone","status":"publish","type":"post","link":"https:\/\/www.angulartraining.com\/daily-newsletter\/angular-17-signals-server-side-rendering-and-standalone\/","title":{"rendered":"Angular 17: Signals, Server-side rendering, and Standalone"},"content":{"rendered":"\n

We’re not done with Angular 17 updates! Here are a few more updates on Signals, Standalone<\/a>, and Server-side rendering.<\/p>\n\n\n\n

Signals<\/h2>\n\n\n\n

Signals have graduated from developer preview and are now officially part of the framework, except the effect<\/code> function<\/a> that is still being tweaked by the Angular team. A big step for Angular Signals.<\/p>\n\n\n\n

Standalone<\/h2>\n\n\n\n

With Angular 17, a new Angular app is generated with standalone components by default. You can upgrade your Angular CLI<\/a> to test that out, and if you don’t want to use standalone by default and your new apps, this feature can be turned off in angular.json with the following config:<\/p>\n\n\n

   \"projects\"<\/span>: {\n    \"my-app\"<\/span>: {\n      \"schematics\"<\/span>: {\n        \"@schematics\/angular:component\"<\/span>: {\n          \"standalone\"<\/span>: false<\/span>\n        }\n     <\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Server-side rendering<\/h2>\n\n\n\n
With Angular 17, you can create an app that uses server-side rendering<\/a> with a single command:<\/p>\n\n\n\n
 ng new --ssr<\/code><\/p>\n\n\n\n
If you want to add server-side rendering to an existing app, you can run: <\/p>\n\n\n\n
ng add @angular\/ssr<\/code><\/p>\n\n\n\n
It’s also possible to pre-render an Angular app using:<\/p>\n\n\n\n
ng build --prerender<\/code><\/p>\n\n\n\n
That way, you don’t need Node.js hosting and can use static, pre-rendered HTML files. I’ll explore this more in the newsletter before the end of the year.<\/p>\n\n\n\n
On that same topic of server-side rendering, hydration graduated developer preview, which means an app rendered on the server side won’t rebuild its entire DOM in the browser. Instead, Angular will take over that DOM and re-hydrate it with up-to-date data as needed.<\/p>\n","protected":false},"excerpt":{"rendered":"
We’re not done with Angular 17 updates! Here are a few more updates on Signals, Standalone, and Server-side rendering. Signals Signals have graduated from developer preview and are now officially part of the framework, except the effect function that is still being tweaked by the Angular team. A big step for Angular Signals. Standalone With […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,39,29,23],"tags":[],"class_list":["post-1790","post","type-post","status-publish","format-standard","hentry","category-angular","category-server-side-rendering","category-signals","category-standalone"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t