microfrontends
/microfrontends
Prowadzi przez budowę, konfigurację i wdrażanie microfrontendów na Vercel: multi-zones, microfrontends.json, lokalny proxy i routing między projektami.
- Autor
- vercel ↗
- Repozytorium
- vercel-plugin ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 23.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 8
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 23.10.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Prowadzi przez budowę, konfigurację i wdrażanie microfrontendów na Vercel: multi-zones, microfrontends.json, lokalny proxy i routing między projektami.
Oryginalny opis (EN)
Guide for building, configuring, and deploying microfrontends on Vercel. Use this skill when the user mentions microfrontends, multi-zones, splitting an app across teams, independent deployments, cross-app routing, incremental migration, composing multiple frontends under one domain, microfrontends.json, @vercel/microfrontends, the microfrontends local proxy, or path-based routing between Vercel projects. Also use when the user asks about shared layouts across projects, navigation between microfrontends, fallback environments, asset prefixes, or feature flag controlled routing.
Jak działa
- Finding Detailed Information
Podgląd SKILL.md
---
name: microfrontends
description: Guide for building, configuring, and deploying microfrontends on Vercel. Use this skill when the user mentions microfrontends, multi-zones, splitting an app across teams, independent deployments, cross-app routing, incremental migration, composing multiple frontends under one domain, microfrontends.json, @vercel/microfrontends, the microfrontends local proxy, or path-based routing between Vercel projects. Also use when the user asks about shared layouts across projects, navigation between microfrontends, fallback environments, asset prefixes, or feature flag controlled routing.
metadata:
priority: 7
docs:
- "https://vercel.com/docs/microfrontends"
pathPatterns:
- 'microfrontends.json'
- 'microfrontends.jsonc'
- 'apps/*/microfrontends.json'
- 'apps/*/microfrontends.jsonc'
bashPatterns:
- '\bvercel\s+microfrontends\b'
- '\bvercel\s+mf\b'
- '\bnpm\s+(install|i|add)\s+[^\n]*@vercel/microfrontends\b'
- '\bpnpm\s+(install|i|add)\s+[^\n]*@vercel/microfrontends\b'
- '\bbun\s+(install|i|add)\s+[^\n]*@vercel/microfrontends\b'
- '\byarn\s+add\s+[^\n]*@vercel/microfrontends\b'
importPatterns:
- '@vercel/microfrontends'
retrieval:
aliases:
- microfrontends
- multi-zones
- multi zones
- mfe
- microfrontend routing
- cross-zone navigation
intents:
- split app into microfrontends
- set up microfrontends
- configure microfrontends.json
- add path routing between projects
- share layout across microfrontends
entities:
- microfrontends.json
- "@vercel/microfrontends"
- default app
- child app
- asset prefix
- microfrontends group
chainTo:
-
pattern: 'runMicrofrontendsMiddleware|flag.*microfrontend|microfrontend.*flag'
targetSkill: routing-middleware
message: 'Flag-controlled microfrontend routing requires middleware in the default app — loading Routing Middleware guidance.'
---
# Vercel Microfrontends
Split a large application into independently deployable units that render as one cohesive app. Vercel handles routing on its global network using `microfrontends.json`.
**Core concepts:** default app (has `microfrontends.json`, serves unmatched requests) · child apps (have `routing` path patterns) · asset prefix (prevents static-asset collisions) · independent deployments.
**Frameworks:** Next.js (App Router + Pages Router), SvelteKit, React Router, Vite — all via `@vercel/microfrontends`.
**CLI (`vercel microfrontends` / `vercel mf`):**
- `create-group` — create a new group; interactive by default, or fully non-interactive with `--non-interactive` (options: `--name`, `--project` (repeatable), `--default-app`, `--default-route`, `--project-default-route` (repeatable, format: `<project>=<route>`, required for each non-default project in non-interactive mode), `--yes` to skip confirmation prompt); note: `--non-interactive` is blocked if adding the projects would exceed the free tier limit — the user must confirm billing changes interactively
- `add-to-group` — add the current project to an existing group; always asks for confirmation (there is no `--yes`), so it needs an interactive terminal, and it refuses to run with `--non-interactive` when adding would go past the free project limit (options: `--group` and `--default-route` pre-fill the prompts)
- `remove-from-group` — remove the current project from its group; without `--yes` it needs an interactive terminal (option: `--yes` skips the project-link prompt and removal confirmations, including the warning for projects still referenced in `microfrontends.json`)
- `delete-group` — delete a group and all its settings, irreversible; without `--yes` it needs an interactive terminal (options: `--group` to pre-select group, `--yes` skips the deletion confirmation; pass both to delete without prompts)
- `inspect-group` — retrieve group metadata (project names, frameworks, git repos, root dirs); useful for automating setup (options: `--group`, `--format=json`, `--config-file-name`)
- `pull` — pull remote `microfrontends.json` for local development (option: `--dpl`)
- `microfrontends proxy` — local dev proxy · `microfrontends port` — print auto-assigned port
## Finding Detailed Information
This skill includes detailed reference docs in the `references/` directory. **Do not read all references upfront.** Instead, search or grep the relevant file when the user asks about a specific topic:
| Topic | Reference file |
|---|---|
| Getting started, quickstart, framework setup, `microfrontends.json` schema, fields, naming, examples | `references/configuration.md` |
| Path expressions, asset prefixes, flag-controlled routing, middleware | `references/path-routing.md` |
| Local proxy setup, polyrepo config, Turborepo, ports, deployment protection | `references/local-development.md` |
| Inspecting groups (`inspect-group`), adding/removing projects, fallback environments, navigation, observability | `references/managing-microfrontends.md` |
| Testing utilities (`validateMiddlewareConfig`, `validateRouting`, etc.), debug headers, common issues | `references/troubleshooting.md` |
| Deployment protection, Vercel Firewall, WAF rules for microfrontends | `references/security.md` |
When the user asks about a specific topic, use grep or search over the relevant reference file to find the answer without loading all references into context.
Pliki w paczce (8)
- .vercel.approvers 1 KB
- SKILL.md 5 KB
- references/configuration.md 7 KB
- references/local-development.md 6 KB
- references/managing-microfrontends.md 8 KB
- references/path-routing.md 6 KB
- references/security.md 5 KB
- references/troubleshooting.md 8 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · vercel/vercel-plugin | 100 | Apache-2.0 |
| vercel-labs/vercel-plugin | 100 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki 9b4d71e22fef (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100vercel-microfrontends
Prowadzi budowę, konfigurację i wdrażanie mikrofrontendów na Vercel: multi-zones, microfrontends.json, lokalny proxy i routing po ścieżkach między projektami. - 100local-microfrontends-a11864af
Pomaga budować i wdrażać mikrofrontendy na Vercelu: trasy między aplikacjami, migrację etapami i wspólną domenę. - 100vercel-cli
Prowadzi wdrożenia, konfigurację i rozwiązywanie problemów z Vercel CLI: CI, logi, metryki, zmienne, domeny i reguły WAF. - 100vercel-services
Konfiguruje i naprawia Vercel Services, czyli kilka frontendów i backendów w jednym projekcie, w tym przepisywania w vercel.json. - 100vercel
Wdraża aplikacje na Vercel i zarządza nimi, w tym wdrożeniami preview i ochroną wdrożeń. - 100vercel-services
Konfiguruje i diagnozuje Vercel Services dla wielu frontendów i backendów w jednym projekcie: klucz services, rewrites, powiązania usług w vercel.json i vercel dev.