Vue Router Integration

Vue Router Integration Overview

At its core, vue router integration is about doing one thing well inside your single-spa project. Once you understand the pattern, you can apply it consistently across features and teams.

Good vue router integration pays off across the whole codebase: fewer surprises, easier testing, and smoother onboarding. The snippet below is a solid starting point.

import { h, createApp } from 'vue';
import singleSpaVue from 'single-spa-vue';
import App from './App.vue';

const vueLifecycles = singleSpaVue({
  createApp,
  appOptions: { render: () => h(App) },
});

export const { bootstrap, mount, unmount } = vueLifecycles;

single-spa-vue turns a Vue app into mountable single-spa lifecycles.

Vue Router Integration Example

registerApplication({
  name: '@org/app',
  app: () => System.import('@org/app'),
  activeWhen: ['/app'],
});
start();

• Start from a minimal Vue Router Integration example and grow it only as needed.
• Keep configuration explicit so Vue Router Integration behaves the same in every environment.
• Name things clearly so teammates understand your Vue Router Integration at a glance.
• Add tests around Vue Router Integration early to lock in expected behaviour.

Single-SPA Cheatsheet

Core single-spa APIs related to vue router integration.

How Vue Router Integration Works in Single-SPA

Vue Router Integration is part of how single-spa lets multiple applications — even in different frameworks — coexist on one page. A root config registers each app and controls when it is active.

single-spa-vue turns a Vue app into mountable single-spa lifecycles.

• A root config registers apps and calls start().
• Each app exports bootstrap, mount, and unmount lifecycles.
• activeWhen decides which routes each app owns.
• Import maps resolve each app's bundle at runtime.

Practical Guidance for Vue Router Integration

For reliable micro frontends, vue router integration should isolate failures and keep shared state minimal. Let each team own its app end to end while agreeing on a few shared contracts.

Common Mistakes

• Copying vue router integration snippets without understanding what each line does.
• Skipping error handling and edge cases when wiring up vue router integration.
• Leaving vue router integration untested, so regressions slip into production.
• Over-engineering vue router integration before you actually need the extra flexibility.

Key Takeaways

• Vue Router Integration is a core part of working effectively with single-spa.
• Start small and keep vue router integration focused on a single responsibility.
• Apply consistent patterns so vue router integration scales across your project.
• Test and document vue router integration to keep it maintainable over time.