Migration guides

Use these guides when updating an existing O3 frontend module or distribution to a newer framework, workspace, test, or build-tool baseline.

Which guide do I need?

• Core v10: Use this when moving modules to Core v10, which ships with Reference Application 3.7.0. It covers development-only import map overrides and stricter login redirects.
• Core v9: Use this when moving modules to the Core v9 framework baseline.
• Rspack and Vitest: Use this when a module has already completed the Core v6 migration and needs to move from Webpack/Jest to Rspack/Vitest.
• Workspace v2: Use this when replacing deprecated workspace v1 APIs such as launchWorkspace, ActionMenuButton, workspace type, canHide, or promptBeforeClosing.
• Core v6: Use this for older modules that still need the Core v6 framework updates before moving to the newer build and test tooling.
• Core v5: Use this for legacy modules that still register pages, extensions, or dynamic metadata using pre-Core v5 patterns.

For actively maintained modules, the usual path is Core v6, then Rspack and Vitest, then each newer framework migration in order: Core v9 and Core v10. Workspace v2 can be done independently when a module uses workspaces.