You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/docs-app/docs/guides/migrating-v2-to-v3.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -158,4 +158,4 @@ Keep automated migration tooling focused on the breaking changes above:
158
158
- rewrite only the legacy `@analogjs/vite-plugin-angular/setup-vitest` setup import
159
159
- flag `@analogjs/trpc` as a removed package that needs a manual migration plan
160
160
- flag `experimental.useAnalogCompiler`, `analogCompilationMode`, and `@analogjs/angular-compiler` as unsupported on the current v3 alpha line rather than removed outright
161
-
- treat optional helpers such as `withTypedRouter`, `withRouteContext`, `withLoaderCaching`, `withDebugRoutes`, and compatibility aliases such as `hmr` as opt-in rather than mandatory rewrites
161
+
- treat optional helpers such as `withTypedRouter`, `withRouteContext`, `withLoaderCaching`, `withDebugRoutes`, and `liveReload` as opt-in rather than mandatory rewrites
Angular supports HMR where in most cases components can be updated without a full page reload. In Analog, use `liveReload` to control the Angular live-reload pipeline.
194
194
195
-
This is separate from Vite's `server.hmr` option, which configures the HMR websocket transport. You can use `server.hmr` together with `liveReload` when you need custom host, port, or path settings.`hmr` is still accepted as a compatibility alias for `liveReload`.
195
+
This is separate from Vite's `server.hmr` option, which configures the HMR websocket transport. You can use `server.hmr` together with `liveReload` when you need custom host, port, or path settings.
196
196
197
-
Analog requires Angular v19 or newer for `liveReload`/ `hmr`to work. On Angular v17-v18, `liveReload`and its `hmr` alias are forcibly disabled at runtime with a console warning, so HMR is unavailable on those versions.
197
+
Analog requires Angular v19 or newer for `liveReload` to work. On Angular v17-v18, `liveReload`is forcibly disabled at runtime with a console warning, so HMR is unavailable on those versions.
Copy file name to clipboardExpand all lines: apps/docs-app/docs/integrations/storybook/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ export default config;
93
93
94
94
For current Analog projects, use `framework.options.liveReload` to control Analog's Angular live-reload behavior.
95
95
96
-
This is separate from Vite's `server.hmr` option, which configures the HMR websocket transport. You can use `server.hmr` together with `framework.options.liveReload` when Storybook needs custom host, port, or path settings.`framework.options.hmr` is still accepted as a compatibility alias.
96
+
This is separate from Vite's `server.hmr` option, which configures the HMR websocket transport. You can use `server.hmr` together with `framework.options.liveReload` when Storybook needs custom host, port, or path settings.
97
97
98
98
Remove the existing `webpackFinal` config function if present.
Copy file name to clipboardExpand all lines: apps/docs-app/docs/integrations/tailwind/index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -124,9 +124,9 @@ Without `prefixes`, Analog falls back to its default Tailwind usage detection fo
124
124
125
125
Use `liveReload` when you need to configure Analog's Angular live-reload behavior explicitly.
126
126
127
-
Vite's `server.hmr` option is separate. It controls the HMR websocket transport, so you can use `server.hmr` together with `liveReload` when your dev server needs custom host, port, or path settings.`hmr` is still accepted as a compatibility alias for `liveReload`.
127
+
Vite's `server.hmr` option is separate. It controls the HMR websocket transport, so you can use `server.hmr` together with `liveReload` when your dev server needs custom host, port, or path settings.
128
128
129
-
Angular HMR requires Angular v19 or newer. On Angular v17-v18, `liveReload`and its `hmr` alias are intentionally disabled at runtime and emit a console warning, so HMR is unavailable on those versions. For broader migration guidance, see the [migration guide](/docs/guides/migrating).
129
+
Angular HMR requires Angular v19 or newer. On Angular v17-v18, `liveReload`is intentionally disabled at runtime and emits a console warning, so HMR is unavailable on those versions. For broader migration guidance, see the [migration guide](/docs/guides/migrating).
130
130
131
131
Tailwind support does not require you to enable HMR manually. The stylesheet pipeline is handled independently from whether Angular can produce a hot component update for a given edit.
Copy file name to clipboardExpand all lines: packages/storybook-angular/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,7 +125,7 @@ Storybook does not automatically infer the Tailwind plugin from your app's `vite
125
125
126
126
Angular reload behavior is controlled with `framework.options.liveReload`.
127
127
128
-
This is separate from Vite's `server.hmr` option, which configures the HMR websocket transport. You can use `server.hmr` together with `framework.options.liveReload` when Storybook needs custom host, port, or path settings.`framework.options.hmr` is still accepted as a compatibility alias.
128
+
This is separate from Vite's `server.hmr` option, which configures the HMR websocket transport. You can use `server.hmr` together with `framework.options.liveReload` when Storybook needs custom host, port, or path settings.
0 commit comments