angular/ssr-browser-globals

Dlaczego

With SSR or prerendering, constructors, ngOnInit, services and computed() run in Node, where window, document and localStorage do not exist. A direct access throws during rendering: the page fails to render on the server or the build fails while prerendering.

Poprawka

Inject DOCUMENT from @angular/core for the document, and put browser-only work (measuring, localStorage, third-party widgets) in afterNextRender() or afterEveryRender(), which run only in the browser. Do not branch the template on isPlatformBrowser; that renders different markup on server and client and breaks hydration. Manual because the engine does not read .ts files: search them for window., document., localStorage and navigator. when the project uses @angular/ssr.

Przykłady

// bad
ngOnInit() { this.theme = localStorage.getItem('theme') ?? 'light' }
// good
constructor() { afterNextRender(() => this.theme.set(localStorage.getItem('theme') ?? 'light')) }

Źródła

• Angular, Server-side and hybrid rendering (authoring server-compatible components)

Przeczytaj w terminalu

npx github:dawidolko/frontend-skills explain angular/ssr-browser-globals