{"owner":"umijs","repo":"qiankun","hasSkills":true,"totalSkillsCount":19,"totalTokensCount":19135,"categories":["anthropic-skill","root-instruction","claude-rule","plugin-manifest"],"hasMcp":false,"mcpConfig":null,"found":[".claude/skills/release-changelog/SKILL.md","AGENTS.md","CLAUDE.md","packages/bundler-plugin/README.md","packages/loader/AGENTS.md","packages/loader/README.md","packages/loader/src/writable-dom/README.md","packages/qiankun/README.md","packages/sandbox/AGENTS.md","packages/sandbox/README.md","packages/shared/AGENTS.md","packages/shared/README.md","packages/single-spa/README.md","packages/ui-bindings/react/README.md","packages/ui-bindings/shared/README.md","packages/ui-bindings/vue/README.md","skills/qiankun/SKILL.md","skills/qiankun/references/create-main-app.md","skills/qiankun/references/create-micro-app.md"],"skills":{".claude/skills/release-changelog/SKILL.md":"---\nname: release-changelog\ndescription: Polish a published qiankun GitHub Release's aggregated notes into a bilingual (English then Chinese) write-up with an agent. Use after a release goes out — turning the mechanically-aggregated, per-package release notes into a clean, human-readable, English + Chinese write-up (highlights, de-duped cross-package lines, clearer wording) via `gh release edit`. Triggers include \"polish the release notes\", \"clean up the GitHub release\", \"improve the changelog for the latest release\".\n---\n\n# Release changelog\n\nQiankun releases are commit-driven: CI auto-derives changesets from Conventional Commits, changesets writes each sub-package's own `CHANGELOG.md` (so npm shows a per-package changelog), and on publish `scripts/generate-release-notes.mjs` aggregates those into **one GitHub Release** per version.\n\nThat aggregated Release is **mechanical** (raw per-package changelog lines). This skill polishes it into a human-readable, **bilingual** write-up — an English version on top, a Chinese version below — after the fact, directly on the GitHub Release, without touching any committed changelog. Read `.changeset/README.md` for the surrounding flow.\n\n## When to run\n\nAfter a release has been published (the \"Version Packages\" PR was merged and CI created the GitHub Release). Typically: \"polish the latest release notes\".\n\n## Steps\n\n1. **Find the release to polish** (default: the most recent one):\n\n ```bash\n gh release list --limit 5\n gh release view --json tagName,name,body\n ```\n\n Confirm the target tag with the user if it's not obviously the latest.\n\n2. **Read the mechanical notes** from the release `body`. This is the raw material — the aggregated per-package changelog. Do not invent anything not present in it (cross-check against `git log ..` only to understand, not to add unlisted changes).\n\n3. **Polish** the notes, keeping the per-package structure so consumers still see each sub-package and its version. Polishing means:\n - Lead with a short **Highlights** list (2–5 bullets) when the release has notable user-facing changes; skip it for small patch releases.\n - Rewrite terse lines into clear, user-facing wording; keep the `(#PR)` reference at the end of each line.\n - De-duplicate: a change that touched many packages is often better stated once under the facade `qiankun` section than repeated under every package.\n - Drop noise (pure \"Updated dependencies\" internal bumps).\n\n4. **Produce a bilingual document** — the full **English** version first, then the full **简体中文** version, separated by a `---` rule. Keep the identical per-package structure and `(#PR)` references in both halves; translate the prose (highlights, descriptions), never the package names, versions, or PR numbers. Template:\n\n ```markdown\n \n\n ## Highlights\n\n - ...\n\n ## qiankun ``\n\n - ...\n\n ---\n\n \n\n ## 更新亮点\n\n - ...\n\n ## qiankun ``\n\n - ...\n ```\n\n5. **Show the user the proposed notes** and get approval.\n\n6. **Update the release** (does not re-tag or re-publish npm):\n\n ```bash\n gh release edit --notes-file \n ```\n\n## Do not\n\n- Do not run `gh release create`, re-tag, or re-publish to npm — only edit the notes of an existing release.\n- Do not edit any `CHANGELOG.md` or `.changeset/*` — the per-package changelogs are the committed record; this skill only refines the GitHub Release prose.\n- Do not add changes that aren't in the mechanical notes / commit history.\n","AGENTS.md":"# QIANKUN PROJECT KNOWLEDGE BASE\n\n**Updated:** 2026-07-06 · **Commit:** dcc42ae4 · **Branch:** next (qiankun 3.0, active dev)\n\nQiankun is a micro-frontend framework built on [single-spa](https://github.com/single-spa/single-spa). v3 rewrites the runtime around **streaming HTML-entry loading**, a **Proxy-membrane JS sandbox**, and native **ESM-sandbox** execution. It is a pnpm monorepo built with Vite 8; `tsc` emits package declarations.\n\n> Requires Node `^22.15 || >=24`, `pnpm@11.13.1` (see `packageManager`). Never use npm/yarn at the root.\n\n## STRUCTURE\n\n```\nqiankun/\n├── packages/\n│ ├── qiankun/ # Facade: public APIs (register/loadMicroApp, start, prefetch) + loadApp orchestration\n│ ├── sandbox/ # JS isolation: Proxy membrane + Compartment → packages/sandbox/AGENTS.md\n│ ├── loader/ # Streaming HTML-entry loader (writable-dom) → packages/loader/AGENTS.md\n│ ├── shared/ # Transpilers, fetch-utils, module-resolver, ESM-sandbox engine → packages/shared/AGENTS.md\n│ ├── single-spa/ # Vendored single-spa fork (@qiankunjs/single-spa, upstream 7.0 @ ce0f925a) → packages/single-spa/README.md\n│ ├── ui-bindings/ # components: react/ vue/ shared/ (dogfooded by examples/{main,vue-host})\n│ └── bundler-plugin/ # Webpack(4/5) + Vite plugins: mark entry script, fix output library\n├── skills/ # Agent skills (installed by users via `npx skills add umijs/qiankun`) — content, not code: no build/publish\n├── e2e/ # Playwright, runs against BUILT dist → e2e/README.md\n├── examples/ # Runnable demos: two hosts (main = @qiankunjs/react, vue-host = @qiankunjs/vue) + react/vue/purehtml/webpack\n└── docs/ # VitePress site (docs/rfcs holds design RFCs)\n```\n\n## PROGRESSIVE DISCLOSURE — read the scoped doc before editing a package\n\n| Working in… | Read first |\n| --- | --- |\n| `packages/sandbox/**` | [`packages/sandbox/AGENTS.md`](packages/sandbox/AGENTS.md) — membrane, compartment, patchers, ESM globals |\n| `packages/loader/**` | [`packages/loader/AGENTS.md`](packages/loader/AGENTS.md) — streaming pipeline, head virtualization |\n| `packages/shared/**` | [`packages/shared/AGENTS.md`](packages/shared/AGENTS.md) — transpilers, fetch decorators, **esm-sandbox** |\n| `e2e/**` | [`e2e/README.md`](e2e/README.md) — Playwright layout, fixtures, anti-flake rules |\n\n## ARCHITECTURE (big picture)\n\n`loadApp` (`packages/qiankun/src/core/loadApp.ts`) is the orchestrator. Per micro-app it wires:\n\n1. **fetch** — decorated `window.fetch`: `makeFetchCacheable(makeFetchRetryable(makeFetchThrowable(fetch)))`.\n2. **sandbox** — `createSandbox()` builds a Proxy-membrane `window`/`document` view; patchers (dynamicAppend, timers, listeners, history) each return a `free()` cleanup called on unmount. Without a container it uses the JS-only preset; a container enables DOM containment.\n3. **loader** — `loadEntry(entry, container, opts)` streams the HTML entry through `writable-dom`, virtualizing `` → `` and running each node through a `nodeTransformer`.\n4. **transpilers** (`shared/assets-transpilers`) rewrite each script/link/style node before it hits live DOM.\n\nMicro apps sharing one container element take FIFO turns for their DOM writes through the **container occupancy gate** (`core/containerOccupancy.ts`, two critical sections: load-phase streaming and mount→unmount; see `docs/rfcs/container-occupancy-gate.md`).\n\nTwo execution paths, chosen per script type:\n\n- **Classic** (`\n\n```\n\nWhen enabling the sub-application loading animation or error capturing capabilities, an additional style class `wrapperClassName` is accepted by the sub-application. The rendered result is as follows:\n\n```vue\n
\n \n \n \n
\n```\n\n### Loading Animation\n\nAfter enabling this feature, a loading animation will automatically be displayed while the sub-application is loading. When the sub-application finishes mounting and becomes in the MOUNTED state, the loading state ends, and the sub-application content is displayed.\n\nSimply pass `autoSetLoading` as a parameter:\n\n```vue\n\n\n```\n\n#### Custom Loading Animation\n\nIf you wish to override the default loading animation style, you can customize the loading component by using the loader slot as the sub-application's loading animation.\n\n```vue\n\n\n```\n\nHere, `loading` is a boolean type parameter; when true, it indicates that it is still in the loading state, and when false, it indicates that the loading state has ended.\n\n### Error Capturing\n\nAfter enabling this feature, when the sub-application encounters an exception while loading, an error message will automatically be displayed. You can pass the `autoCaptureError` property to the sub-application to enable error capturing capabilities:\n\n```vue\n\n\n```\n\n#### Custom Error Capturing\n\nIf you wish to override the default error capturing component style, you can customize the error capturing component for the sub-application using the errorBoundary slot:\n\n```vue\n\n\n```\n\n### Component Properties\n\n| Property | Required | Description | Type | Default Value |\n| --- | --- | --- | --- | --- |\n| `name` | Yes | The name of the micro-application | `string` | |\n| `entry` | Yes | The HTML address of the micro-application | `string` | |\n| `settings` | No | qiankun configuration for this micro-application — sandbox, style isolation, fetch, … | `AppConfiguration` | `{ sandbox: true }` |\n| `lifeCycles` | No | qiankun lifecycle hooks for this micro-application. They are captured on the first load into a given container, so avoid closing over component state in them | `LifeCycles` | `undefined` |\n| `autoSetLoading` | No | Automatically set the loading status of the micro-application | `boolean` | `false` |\n| `autoCaptureError` | No | Automatically set error capturing for the micro-application | `boolean` | `false` |\n| `className` | No | The style class for the micro-application | `string` | `undefined` |\n| `wrapperClassName` | No | The style class wrapping the micro-application's loading and error components | `string` | `undefined` |\n| `appProps` | No | Properties passed to the sub-application | `Record` | `undefined` |\n\n### Component Slots\n\n| Slot | Slot props | Description |\n| ---------------------------------- | ---------------------- | -------------------- |\n| `loader` | `{ loading: boolean }` | Loading state slot |\n| `errorBoundary` / `error-boundary` | `{ error: Error }` | Error capturing slot |\n\nVue does not normalize slot names the way it normalizes props, so both spellings of the error slot are accepted. Unlike the React binding, this component's wrapper is not positioned — give it a positioned class through `wrapperClassName` if your slot renders an overlay.\n","skills/qiankun/SKILL.md":"---\nname: qiankun\ndescription: >-\n Usage manual for building micro-frontend projects with qiankun 3.x. Use when the user wants to create a qiankun main (host) app or sub (micro) app, convert an existing Vite app into a qiankun micro app, or wire up micro-frontend loading with React/Vue.\n---\n\n# qiankun\n\nqiankun is a micro-frontend framework: a main (host) app loads sub (micro) apps from their HTML entries at runtime, each inside a JS sandbox, with opt-in CSS isolation. This skill is the agent-facing manual for **qiankun 3.x**.\n\n## Task routing\n\nRead only the reference file(s) the task at hand needs:\n\n| Task | Read |\n| --- | --- |\n| Create a micro (sub) app, or convert an existing Vite app | [references/create-micro-app.md](references/create-micro-app.md) |\n| Create a main (host) app | [references/create-main-app.md](references/create-main-app.md) |\n| Anything else — migration, style isolation, sandbox, debugging | https://qiankun.umijs.org and `examples/` in https://github.com/umijs/qiankun |\n\n## Before you start\n\nDetermine these, asking the user only when not inferable from context:\n\n1. **App type** — main (host/shell) or sub (micro app).\n2. **App name** — lowercase letters, numbers, hyphens. The name the host registers must exactly match the name the sub app uses in its classic-mode fallback.\n3. **Framework** — React or Vue; TypeScript or JavaScript. Templates in the references are TS; strip types for JS.\n4. **Dev port** — must be fixed and unique per app, because the host hard-references it in `entry`. Convention: main app `7099`, sub apps `7101`, `7102`, …\n\nPackage versions — until qiankun 3.0 stable ships, `rc` is the dist-tag for the core packages:\n\n| Package | Dist-tag | Goes in |\n| ------------------------------------- | -------- | --------------------------------------------- |\n| `qiankun` | `rc` | main app `dependencies` |\n| `@qiankunjs/react` / `@qiankunjs/vue` | `rc` | main app `dependencies` (optional UI binding) |\n| `@qiankunjs/bundler-plugin` | `rc` | sub app `devDependencies` |\n\n## Key facts\n\nThese invariants shape every task below:\n\n- **Vite sub apps need no dedicated build mode.** qiankun 3 loads `\n\n```\n\nWhen enabling the sub-application loading animation or error capturing capabilities, an additional style class `wrapperClassName` is accepted by the sub-application. The rendered result is as follows:\n\n```vue\n
\n \n \n \n
\n```\n\n### Loading Animation\n\nAfter enabling this feature, a loading animation will automatically be displayed while the sub-application is loading. When the sub-application finishes mounting and becomes in the MOUNTED state, the loading state ends, and the sub-application content is displayed.\n\nSimply pass `autoSetLoading` as a parameter:\n\n```vue\n\n\n```\n\n#### Custom Loading Animation\n\nIf you wish to override the default loading animation style, you can customize the loading component by using the loader slot as the sub-application's loading animation.\n\n```vue\n\n\n```\n\nHere, `loading` is a boolean type parameter; when true, it indicates that it is still in the loading state, and when false, it indicates that the loading state has ended.\n\n### Error Capturing\n\nAfter enabling this feature, when the sub-application encounters an exception while loading, an error message will automatically be displayed. You can pass the `autoCaptureError` property to the sub-application to enable error capturing capabilities:\n\n```vue\n\n\n```\n\n#### Custom Error Capturing\n\nIf you wish to override the default error capturing component style, you can customize the error capturing component for the sub-application using the errorBoundary slot:\n\n```vue\n\n\n```\n\n### Component Properties\n\n| Property | Required | Description | Type | Default Value |\n| --- | --- | --- | --- | --- |\n| `name` | Yes | The name of the micro-application | `string` | |\n| `entry` | Yes | The HTML address of the micro-application | `string` | |\n| `settings` | No | qiankun configuration for this micro-application — sandbox, style isolation, fetch, … | `AppConfiguration` | `{ sandbox: true }` |\n| `lifeCycles` | No | qiankun lifecycle hooks for this micro-application. They are captured on the first load into a given container, so avoid closing over component state in them | `LifeCycles` | `undefined` |\n| `autoSetLoading` | No | Automatically set the loading status of the micro-application | `boolean` | `false` |\n| `autoCaptureError` | No | Automatically set error capturing for the micro-application | `boolean` | `false` |\n| `className` | No | The style class for the micro-application | `string` | `undefined` |\n| `wrapperClassName` | No | The style class wrapping the micro-application's loading and error components | `string` | `undefined` |\n| `appProps` | No | Properties passed to the sub-application | `Record` | `undefined` |\n\n### Component Slots\n\n| Slot | Slot props | Description |\n| ---------------------------------- | ---------------------- | -------------------- |\n| `loader` | `{ loading: boolean }` | Loading state slot |\n| `errorBoundary` / `error-boundary` | `{ error: Error }` | Error capturing slot |\n\nVue does not normalize slot names the way it normalizes props, so both spellings of the error slot are accepted. Unlike the React binding, this component's wrapper is not positioned — give it a positioned class through `wrapperClassName` if your slot renders an overlay.\n","skills/qiankun/SKILL.md":"---\nname: qiankun\ndescription: >-\n Usage manual for building micro-frontend projects with qiankun 3.x. Use when the user wants to create a qiankun main (host) app or sub (micro) app, convert an existing Vite app into a qiankun micro app, or wire up micro-frontend loading with React/Vue.\n---\n\n# qiankun\n\nqiankun is a micro-frontend framework: a main (host) app loads sub (micro) apps from their HTML entries at runtime, each inside a JS sandbox, with opt-in CSS isolation. This skill is the agent-facing manual for **qiankun 3.x**.\n\n## Task routing\n\nRead only the reference file(s) the task at hand needs:\n\n| Task | Read |\n| --- | --- |\n| Create a micro (sub) app, or convert an existing Vite app | [references/create-micro-app.md](references/create-micro-app.md) |\n| Create a main (host) app | [references/create-main-app.md](references/create-main-app.md) |\n| Anything else — migration, style isolation, sandbox, debugging | https://qiankun.umijs.org and `examples/` in https://github.com/umijs/qiankun |\n\n## Before you start\n\nDetermine these, asking the user only when not inferable from context:\n\n1. **App type** — main (host/shell) or sub (micro app).\n2. **App name** — lowercase letters, numbers, hyphens. The name the host registers must exactly match the name the sub app uses in its classic-mode fallback.\n3. **Framework** — React or Vue; TypeScript or JavaScript. Templates in the references are TS; strip types for JS.\n4. **Dev port** — must be fixed and unique per app, because the host hard-references it in `entry`. Convention: main app `7099`, sub apps `7101`, `7102`, …\n\nPackage versions — until qiankun 3.0 stable ships, `rc` is the dist-tag for the core packages:\n\n| Package | Dist-tag | Goes in |\n| ------------------------------------- | -------- | --------------------------------------------- |\n| `qiankun` | `rc` | main app `dependencies` |\n| `@qiankunjs/react` / `@qiankunjs/vue` | `rc` | main app `dependencies` (optional UI binding) |\n| `@qiankunjs/bundler-plugin` | `rc` | sub app `devDependencies` |\n\n## Key facts\n\nThese invariants shape every task below:\n\n- **Vite sub apps need no dedicated build mode.** qiankun 3 loads `\n\n```\n\nWhen enabling the sub-application loading animation or error capturing capabilities, an additional style class `wrapperClassName` is accepted by the sub-application. The rendered result is as follows:\n\n```vue\n
\n \n \n \n
\n```\n\n### Loading Animation\n\nAfter enabling this feature, a loading animation will automatically be displayed while the sub-application is loading. When the sub-application finishes mounting and becomes in the MOUNTED state, the loading state ends, and the sub-application content is displayed.\n\nSimply pass `autoSetLoading` as a parameter:\n\n```vue\n\n\n```\n\n#### Custom Loading Animation\n\nIf you wish to override the default loading animation style, you can customize the loading component by using the loader slot as the sub-application's loading animation.\n\n```vue\n\n\n```\n\nHere, `loading` is a boolean type parameter; when true, it indicates that it is still in the loading state, and when false, it indicates that the loading state has ended.\n\n### Error Capturing\n\nAfter enabling this feature, when the sub-application encounters an exception while loading, an error message will automatically be displayed. You can pass the `autoCaptureError` property to the sub-application to enable error capturing capabilities:\n\n```vue\n\n\n```\n\n#### Custom Error Capturing\n\nIf you wish to override the default error capturing component style, you can customize the error capturing component for the sub-application using the errorBoundary slot:\n\n```vue\n\n\n```\n\n### Component Properties\n\n| Property | Required | Description | Type | Default Value |\n| --- | --- | --- | --- | --- |\n| `name` | Yes | The name of the micro-application | `string` | |\n| `entry` | Yes | The HTML address of the micro-application | `string` | |\n| `settings` | No | qiankun configuration for this micro-application — sandbox, style isolation, fetch, … | `AppConfiguration` | `{ sandbox: true }` |\n| `lifeCycles` | No | qiankun lifecycle hooks for this micro-application. They are captured on the first load into a given container, so avoid closing over component state in them | `LifeCycles` | `undefined` |\n| `autoSetLoading` | No | Automatically set the loading status of the micro-application | `boolean` | `false` |\n| `autoCaptureError` | No | Automatically set error capturing for the micro-application | `boolean` | `false` |\n| `className` | No | The style class for the micro-application | `string` | `undefined` |\n| `wrapperClassName` | No | The style class wrapping the micro-application's loading and error components | `string` | `undefined` |\n| `appProps` | No | Properties passed to the sub-application | `Record` | `undefined` |\n\n### Component Slots\n\n| Slot | Slot props | Description |\n| ---------------------------------- | ---------------------- | -------------------- |\n| `loader` | `{ loading: boolean }` | Loading state slot |\n| `errorBoundary` / `error-boundary` | `{ error: Error }` | Error capturing slot |\n\nVue does not normalize slot names the way it normalizes props, so both spellings of the error slot are accepted. Unlike the React binding, this component's wrapper is not positioned — give it a positioned class through `wrapperClassName` if your slot renders an overlay.\n","isInternal":false,"tokens":1103,"sizeBytes":4798}],"systemPromptSnippet":"\n\n# QIANKUN PROJECT KNOWLEDGE BASE\n\n**Updated:** 2026-07-06 · **Commit:** dcc42ae4 · **Branch:** next (qiankun 3.0, active dev)\n\nQiankun is a micro-frontend framework built on [single-spa](https://github.com/single-spa/single-spa). v3 rewrites the runtime around **streaming HTML-entry loading**, a **Proxy-membrane JS sandbox**, and native **ESM-sandbox** execution. It is a pnpm monorepo built with Vite 8; `tsc` emits package declarations.\n\n> Requires Node `^22.15 || >=24`, `pnpm@11.13.1` (see `packageManager`). Never use npm/yarn at the root.\n\n## STRUCTURE\n\n```\nqiankun/\n├── packages/\n│ ├── qiankun/ # Facade: public APIs (register/loadMicroApp, start, prefetch) + loadApp orchestration\n│ ├── sandbox/ # JS isolation: Proxy membrane + Compartment → packages/sandbox/AGENTS.md\n│ ├── loader/ # Streaming HTML-entry loader (writable-dom) → packages/loader/AGENTS.md\n│ ├── shared/ # Transpilers, fetch-utils, module-resolver, ESM-sandbox engine → packages/shared/AGENTS.md\n│ ├── single-spa/ # Vendored single-spa fork (@qiankunjs/single-spa, upstream 7.0 @ ce0f925a) → packages/single-spa/README.md\n│ ├── ui-bindings/ # components: react/ vue/ shared/ (dogfooded by examples/{main,vue-host})\n│ └── bundler-plugin/ # Webpack(4/5) + Vite plugins: mark entry script, fix output library\n├── skills/ # Agent skills (installed by users via `npx skills add umijs/qiankun`) — content, not code: no build/publish\n├── e2e/ # Playwright, runs against BUILT dist → e2e/README.md\n├── examples/ # Runnable demos: two hosts (main = @qiankunjs/react, vue-host = @qiankunjs/vue) + react/vue/purehtml/webpack\n└── docs/ # VitePress site (docs/rfcs holds design RFCs)\n```\n\n## PROGRESSIVE DISCLOSURE — read the scoped doc before editing a package\n\n| Working in… | Read first |\n| --- | --- |\n| `packages/sandbox/**` | [`packages/sandbox/AGENTS.md`](packages/sandbox/AGENTS.md) — membrane, compartment, patchers, ESM globals |\n| `packages/loader/**` | [`packages/loader/AGENTS.md`](packages/loader/AGENTS.md) — streaming pipeline, head virtualization |\n| `packages/shared/**` | [`packages/shared/AGENTS.md`](packages/shared/AGENTS.md) — transpilers, fetch decorators, **esm-sandbox** |\n| `e2e/**` | [`e2e/README.md`](e2e/README.md) — Playwright layout, fixtures, anti-flake rules |\n\n## ARCHITECTURE (big picture)\n\n`loadApp` (`packages/qiankun/src/core/loadApp.ts`) is the orchestrator. Per micro-app it wires:\n\n1. **fetch** — decorated `window.fetch`: `makeFetchCacheable(makeFetchRetryable(makeFetchThrowable(fetch)))`.\n2. **sandbox** — `createSandbox()` builds a Proxy-membrane `window`/`document` view; patchers (dynamicAppend, timers, listeners, history) each return a `free()` cleanup called on unmount. Without a container it uses the JS-only preset; a container enables DOM containment.\n3. **loader** — `loadEntry(entry, container, opts)` streams the HTML entry through `writable-dom`, virtualizing `` → `` and running each node through a `nodeTransformer`.\n4. **transpilers** (`shared/assets-transpilers`) rewrite each script/link/style node before it hits live DOM.\n\nMicro apps sharing one container element take FIFO turns for their DOM writes through the **container occupancy gate** (`core/containerOccupancy.ts`, two critical sections: load-phase streaming and mount→unmount; see `docs/rfcs/container-occupancy-gate.md`).\n\nTwo execution paths, chosen per script type:\n\n- **Classic** (`\n\n```\n\nWhen enabling the sub-application loading animation or error capturing capabilities, an additional style class `wrapperClassName` is accepted by the sub-application. The rendered result is as follows:\n\n```vue\n
\n \n \n \n
\n```\n\n### Loading Animation\n\nAfter enabling this feature, a loading animation will automatically be displayed while the sub-application is loading. When the sub-application finishes mounting and becomes in the MOUNTED state, the loading state ends, and the sub-application content is displayed.\n\nSimply pass `autoSetLoading` as a parameter:\n\n```vue\n\n\n```\n\n#### Custom Loading Animation\n\nIf you wish to override the default loading animation style, you can customize the loading component by using the loader slot as the sub-application's loading animation.\n\n```vue\n\n\n```\n\nHere, `loading` is a boolean type parameter; when true, it indicates that it is still in the loading state, and when false, it indicates that the loading state has ended.\n\n### Error Capturing\n\nAfter enabling this feature, when the sub-application encounters an exception while loading, an error message will automatically be displayed. You can pass the `autoCaptureError` property to the sub-application to enable error capturing capabilities:\n\n```vue\n\n\n```\n\n#### Custom Error Capturing\n\nIf you wish to override the default error capturing component style, you can customize the error capturing component for the sub-application using the errorBoundary slot:\n\n```vue\n\n\n```\n\n### Component Properties\n\n| Property | Required | Description | Type | Default Value |\n| --- | --- | --- | --- | --- |\n| `name` | Yes | The name of the micro-application | `string` | |\n| `entry` | Yes | The HTML address of the micro-application | `string` | |\n| `settings` | No | qiankun configuration for this micro-application — sandbox, style isolation, fetch, … | `AppConfiguration` | `{ sandbox: true }` |\n| `lifeCycles` | No | qiankun lifecycle hooks for this micro-application. They are captured on the first load into a given container, so avoid closing over component state in them | `LifeCycles` | `undefined` |\n| `autoSetLoading` | No | Automatically set the loading status of the micro-application | `boolean` | `false` |\n| `autoCaptureError` | No | Automatically set error capturing for the micro-application | `boolean` | `false` |\n| `className` | No | The style class for the micro-application | `string` | `undefined` |\n| `wrapperClassName` | No | The style class wrapping the micro-application's loading and error components | `string` | `undefined` |\n| `appProps` | No | Properties passed to the sub-application | `Record` | `undefined` |\n\n### Component Slots\n\n| Slot | Slot props | Description |\n| ---------------------------------- | ---------------------- | -------------------- |\n| `loader` | `{ loading: boolean }` | Loading state slot |\n| `errorBoundary` / `error-boundary` | `{ error: Error }` | Error capturing slot |\n\nVue does not normalize slot names the way it normalizes props, so both spellings of the error slot are accepted. Unlike the React binding, this component's wrapper is not positioned — give it a positioned class through `wrapperClassName` if your slot renders an overlay.\n"}