Saltar al contenido principal

Migrating from Analog v1 to v2

Upgrade the workspace to the current Analog v2 line first, then continue with the v3 guide.

Update the workspace packages​

Use the standard Analog update flow for your workspace type, but target the v2 major:

ng update @analogjs/platform@2

Replace internal content imports​

If your app imports from internal paths such as @analogjs/content/lib, switch those imports to the public @analogjs/content entrypoint.

import { ContentRenderer, type TableOfContentItem } from '@analogjs/content';

Keep content rendering, markdown helpers, and table-of-contents usage on the public API surface before moving on to v3.

Continue to v3​

Once the app is on the current v2 line and using public imports, continue with the Analog v2 to v3 migration guide.