Find the Right SDK

Use this page to quickly pick the Zephyr SDK that matches your stack.

SDK picker

Your stackZephyr SDKGuide link
Vitevite-plugin-zephyr/bundlers/vite
Webpackzephyr-webpack-plugin/bundlers/webpack
Rspackzephyr-rspack-plugin/bundlers/rspack
Rsbuild / Rslibzephyr-rsbuild-plugin/bundlers/rsbuild
Rolluprollup-plugin-zephyr/bundlers/rollup
Rolldownzephyr-rolldown-plugin/bundlers/rolldown
Parcelparcel-reporter-zephyr/bundlers/parcel
Metro (React Native)zephyr-metro-plugin/bundlers/metro
Re.Pack (React Native)zephyr-repack-plugin/bundlers/repack
Astrozephyr-astro-integration/meta-frameworks/astro
Modern.jszephyr-modernjs-plugin/meta-frameworks/modernjs
Rspresszephyr-rspress-plugin/meta-frameworks/rspress
Ember.js (via Vite pipeline)vite-plugin-zephyr/meta-frameworks/emberjs
TanStack Startvite-plugin-tanstack-start-zephyr/meta-frameworks/tanstack-start

Quick decision flow

  1. If your bundler/framework exists in the table, use that SDK and guide.
  2. If you are integrating into an existing app with custom structure, check Existing App Integration.
  3. If you need multi-bundler Module Federation, check Multi-bundler Setup.
  4. If your stack is not listed, use zephyr-agent as a low-level fallback.

Fallback for unsupported stacks

If your framework has no official SDK yet, use uploadOutputToZephyr from zephyr-agent to upload a generated output directory. If you want to integrate with Zephyr on a custom stack, this is the supported integration path.

Best fit:

  • custom framework adapters
  • internal platform tooling
  • plugin maintainers

Minimal usage:

import { uploadOutputToZephyr } from 'zephyr-agent';

await uploadOutputToZephyr({
  rootDir: process.cwd(),
  outputDir: '.output',
  ssr: true,
});

For full fallback behavior (options, mapping, SSR/CSR, errors), see zephyr-agent docs in the packages repository.