Summary

Ports two community packages — antfu/shiki-stream and shikijs/shiki-magic-move — into this monorepo as official @shikijs/* packages.

Implementation and playgrounds are preserved verbatim from upstream; only package identity and monorepo integration changed.

What's in each package

@shikijs/stream — streaming colorization, useful for highlighting LLM output and other text streams. Exposes:

• . — core (CodeToTokenTransformStream, RecallToken, etc.)
• ./vue, ./react, ./solid — renderer components

@shikijs/magic-move — smoothly animated code blocks (used by Slidev). Exposes:

• ./core, ./renderer, ./types, ./style.css — framework-agnostic
• ./vue, ./react, ./solid, ./svelte — framework adapters
• web-component build (reachable via dist/web-component.mjs)

Source rewrites (minimum needed for the rename)

• packages/magic-move/src/index.ts — error message refers to @shikijs/magic-move
• packages/magic-move/src/svelte/*.svelte — cross-subpath imports updated (shiki-magic-move/types → @shikijs/magic-move/types, etc.). These are runtime imports that Svelte's bundler resolves against the published package name, so they have to match the new name.

CSS class names (shiki-magic-move-*, shiki-stream) and custom-element tag names (shiki-magic-move, shiki-magic-move-precompiled, shiki-magic-move-renderer) are kept as-is because they are public CSS / DOM API surfaces — changing them would break downstream consumers.

Monorepo infrastructure changes

• pnpm-workspace.yaml
  • New catalog entries for unbuild, framework Vite plugins (Vue / React / Solid / Svelte), and babel presets (@babel/preset-typescript, @babel/preset-react, babel-preset-solid).
  • Added overrides: { semver: ^7.8.0 } to satisfy the workspace's trustPolicy: no-downgrade — vite-plugin-solid → @babel/core pulls in semver@6.3.1, which lacks provenance. Both upstreams already pin semver to ^7.x in their own resolutions for the same reason.
• tsconfig.json
  • jsx: preserve and allowImportingTsExtensions: true to support the Solid .tsx re-exports (packages/stream/src/solid/index.ts does export * from './renderer.tsx').
  • paths entries for @shikijs/stream{,/vue,/react,/solid} and @shikijs/magic-move{,/core,/renderer,/types,/vue,/react,/solid,/svelte}.
• test/exports.test.ts — extended the existing resolveExportEntries filter to skip framework-adapter subpaths (./vue, ./react, ./solid, ./svelte) because the root vitest env doesn't load the Solid / Svelte / React JSX toolchains. Also skips the @shikijs/magic-move bare entry which intentionally throws by upstream design.
• docs/.vitepress/config.ts — added Stream and Magic Move entries to the INTEGRATIONS array (nav + sidebar).
• New docs pages — docs/packages/stream.md, docs/packages/magic-move.md, modeled on the existing transformers.md / monaco.md pattern.

Verification

• pnpm install ✅ clean
• pnpm -r run build ✅ all 21 workspace packages including both new ones
• pnpm typecheck (vue-tsc) ✅ zero errors
• pnpm exec vitest run packages/stream packages/magic-move test/exports.test.ts ✅ 4 files / 23 tests pass
• Full workspace test run ✅ 77 / 77 files, 606 / 606 tests

Pre-existing notes (not introduced by this PR)

• packages/shiki/test/bundle.test.ts > bundle-full is slow under workspace contention — passes in ~8s in isolation but can time out at the 30s default when the full workspace runs in parallel. Pre-existing flake, not caused by this change.
• Two unrelated snapshots showed drift when I ran vitest -u (engine-javascript record + a Vue grammar HTML snapshot in shiki tests). Both are upstream drift that already exists on main — reverted, out of scope here.

Follow-ups (deliberately out of scope)

• Publish deprecation notices on the old npm packages (shiki-stream, shiki-magic-move) that point at the new @shikijs/* names — needs an explicit release step.
• The playgrounds still link to the original upstream GitHub repos (e.g. https://github.com/antfu/shiki-stream). Kept as-is per the migration spec; easy to update later if you want them to point at this monorepo.