@fern-api/generator-migrations 0.0.1 → 0.0.2

package/lib/generators/typescript/migrations/3.0.0.d.ts

@@ -1,242 +0,0 @@
-import type { Migration } from "@fern-api/migrations-base";
-/**
- * Migration for version 3.0.0
- *
- * ## Context
- *
- * Version 3.0.0 modernized the generated SDK tooling by switching to pnpm and Vitest,
- * which offer better performance, smaller disk usage, and faster test execution compared
- * to yarn and Jest. However, teams with existing workflows may prefer to maintain their
- * current tooling.
- *
- * This migration explicitly sets the old defaults for users upgrading from pre-3.0.0
- * versions, allowing them to continue using yarn and Jest without any changes to their
- * development workflow.
- *
- * ## Changed Defaults
- *
- * | Field | Old Default (pre-3.0.0) | New Default (3.0.0+) | Impact |
- * |-------|-------------------------|----------------------|--------|
- * | `packageManager` | `"yarn"` | `"pnpm"` | Generated package.json uses pnpm for dependency management |
- * | `testFramework` | `"jest"` | `"vitest"` | Generated tests use Vitest instead of Jest |
- *
- * ## Migration Strategy
- *
- * This migration uses the nullish coalescing assignment operator (`??=`) to only set
- * values that are explicitly undefined. This means:
- * - ✅ If a user has explicitly configured a field, that value is preserved
- * - ✅ If a field is undefined, the old default is set
- * - ✅ Users can opt into modern tooling by removing these fields later
- *
- * ## Examples
- *
- * ### Example 1: Empty Config (Migration Applied - Keep Yarn + Jest)
- *
- * **Before Migration (2.9.0 → 3.0.0):**
- * ```yaml
- * generators:
- *   - name: fernapi/fern-typescript-sdk
- *     version: 2.9.0
- *     config: {}
- * ```
- *
- * **After Migration:**
- * ```yaml
- * generators:
- *   - name: fernapi/fern-typescript-sdk
- *     version: 3.0.0
- *     config:
- *       packageManager: yarn    # Set by migration - keeps yarn
- *       testFramework: jest     # Set by migration - keeps jest
- * ```
- *
- * **Result:** Generated SDK continues using yarn and Jest.
- *
- * **Generated Files:**
- * - `package.json` with yarn scripts and Jest config
- * - Test files using Jest syntax (`describe`, `it`, `expect`)
- * - `.yarnrc` or `.yarnrc.yml` if applicable
- *
- * ### Example 2: Adopting Modern Tooling (pnpm + Vitest)
- *
- * **After Initial Migration:**
- * ```yaml
- * generators:
- *   - name: fernapi/fern-typescript-sdk
- *     version: 3.0.0
- *     config:
- *       packageManager: yarn
- *       testFramework: jest
- * ```
- *
- * **To Adopt pnpm + Vitest:**
- * ```yaml
- * generators:
- *   - name: fernapi/fern-typescript-sdk
- *     version: 3.0.0
- *     config: {}  # Remove to use new defaults
- * ```
- *
- * **Result:** Generated SDK uses pnpm and Vitest.
- *
- * **Generated Files:**
- * - `package.json` with pnpm scripts
- * - `vitest.config.ts` for test configuration
- * - Test files using Vitest syntax (compatible with Jest)
- * - `pnpm-workspace.yaml` if applicable
- *
- * ### Example 3: Mixed Tooling (Custom Configuration)
- *
- * **Keep yarn but adopt Vitest:**
- * ```yaml
- * generators:
- *   - name: fernapi/fern-typescript-sdk
- *     version: 3.0.0
- *     config:
- *       packageManager: yarn    # Keep yarn
- *       # testFramework defaults to vitest
- * ```
- *
- * **Keep Jest but adopt pnpm:**
- * ```yaml
- * generators:
- *   - name: fernapi/fern-typescript-sdk
- *     version: 3.0.0
- *     config:
- *       testFramework: jest     # Keep Jest
- *       # packageManager defaults to pnpm
- * ```
- *
- * ## Why These Defaults Changed
- *
- * ### pnpm vs yarn
- *
- * **Performance:**
- * - pnpm install is 2-3x faster than yarn
- * - Uses hard links instead of copying files
- * - Significantly smaller `node_modules` (50-70% reduction)
- *
- * **Correctness:**
- * - Strict dependency resolution prevents phantom dependencies
- * - Better monorepo support with workspaces
- * - More deterministic builds
- *
- * **Ecosystem:**
- * - Growing adoption in major projects (Vue 3, Prisma, Turborepo)
- * - Better compatibility with modern tooling
- *
- * ### Vitest vs Jest
- *
- * **Performance:**
- * - 10-20x faster test execution with native ESM
- * - Built-in watch mode with instant HMR
- * - Parallel test execution by default
- *
- * **Developer Experience:**
- * - Native TypeScript support (no ts-jest needed)
- * - Vite-powered with instant module reloading
- * - Jest-compatible API (easy migration)
- * - Better error messages and stack traces
- *
- * **Modern Features:**
- * - Native ESM support
- * - Web Workers and multi-threading support
- * - In-source testing capabilities
- *
- * ## Compatibility Notes
- *
- * ### Vitest Limitations
- *
- * Vitest is **not compatible** with certain generator configurations:
- *
- * 1. **`useBigInt: true`**: Vitest doesn't handle BigInt serialization the same way as Jest
- *    - **Workaround**: Keep `testFramework: jest` if using BigInt
- *
- * 2. **`streamType: wrapper`**: Older stream wrappers may not work with Vitest's ESM mode
- *    - **Workaround**: Either use `streamType: web` or keep `testFramework: jest`
- *
- * 3. **`packagePath` (custom paths)**: May have module resolution issues with Vitest
- *    - **Workaround**: Keep `testFramework: jest` for complex custom paths
- *
- * If you have any of these configurations, the migration correctly keeps Jest as the test framework.
- *
- * ## Migration Path to Modern Tooling
- *
- * ### Step 1: Upgrade with Migration (Safe)
- * ```bash
- * fern generator upgrade
- * ```
- * Result: Keeps yarn and Jest, no workflow changes needed.
- *
- * ### Step 2: Install pnpm (Optional)
- * ```bash
- * npm install -g pnpm@latest
- * ```
- *
- * ### Step 3: Adopt Modern Tooling (Optional)
- * Edit `generators.yml`:
- * ```yaml
- * config: {}  # Use pnpm + vitest
- * ```
- *
- * ### Step 4: Update CI/CD (Optional)
- * Update CI scripts to use pnpm:
- * ```yaml
- * # GitHub Actions example
- * - uses: pnpm/action-setup@v2
- *   with:
- *     version: 8
- * - run: pnpm install
- * - run: pnpm test
- * ```
- *
- * ### Step 5: Migrate yarn.lock (Optional)
- * ```bash
- * # Convert yarn.lock to pnpm-lock.yaml
- * pnpm import
- * rm yarn.lock
- * ```
- *
- * ## Troubleshooting
- *
- * ### "pnpm: command not found"
- * **Cause:** pnpm not installed globally.
- * **Solution:** Install pnpm: `npm install -g pnpm`
- *
- * ### Vitest errors with BigInt
- * **Cause:** Vitest and BigInt serialization incompatibility.
- * **Solution:** Use `testFramework: jest` in config.
- *
- * ### Module resolution errors with Vitest
- * **Cause:** ESM/CommonJS compatibility issues.
- * **Solution:** Either fix module format or use `testFramework: jest`.
- *
- * ### Tests fail after switching to Vitest
- * **Cause:** Vitest has stricter ESM requirements.
- * **Solution:** Ensure `package.json` has `"type": "module"` or use `.ts` extensions.
- *
- * ## Performance Comparison
- *
- * Based on typical SDK project (50 tests, 1000 LOC):
- *
- * **Install Time:**
- * - yarn: ~15s
- * - pnpm: ~5s (3x faster)
- *
- * **Test Execution:**
- * - Jest: ~8s
- * - Vitest: ~0.8s (10x faster)
- *
- * **Disk Usage:**
- * - yarn: ~200MB node_modules
- * - pnpm: ~80MB node_modules (60% reduction)
- *
- * ## Recommendations
- *
- * - **New projects**: Use the new defaults (pnpm + Vitest)
- * - **Existing projects**: Keep old defaults initially, migrate when convenient
- * - **CI/CD-heavy projects**: Consider pnpm for faster installs
- * - **Projects with BigInt**: Keep Jest until Vitest improves BigInt support
- */
-export declare const migration_3_0_0: Migration;
-//# sourceMappingURL=3.0.0.d.ts.map

package/lib/generators/typescript/migrations/3.0.0.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"3.0.0.d.ts","sourceRoot":"","sources":["../../../../src/generators/typescript/migrations/3.0.0.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,2BAA2B,CAAC;AAG3D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8OG;AACH,eAAO,MAAM,eAAe,EAAE,SAW7B,CAAC"}

package/lib/generators/typescript/migrations/3.0.0.js

@@ -1,250 +0,0 @@
-import { migrateConfig } from "@fern-api/migrations-base";
-/**
- * Migration for version 3.0.0
- *
- * ## Context
- *
- * Version 3.0.0 modernized the generated SDK tooling by switching to pnpm and Vitest,
- * which offer better performance, smaller disk usage, and faster test execution compared
- * to yarn and Jest. However, teams with existing workflows may prefer to maintain their
- * current tooling.
- *
- * This migration explicitly sets the old defaults for users upgrading from pre-3.0.0
- * versions, allowing them to continue using yarn and Jest without any changes to their
- * development workflow.
- *
- * ## Changed Defaults
- *
- * | Field | Old Default (pre-3.0.0) | New Default (3.0.0+) | Impact |
- * |-------|-------------------------|----------------------|--------|
- * | `packageManager` | `"yarn"` | `"pnpm"` | Generated package.json uses pnpm for dependency management |
- * | `testFramework` | `"jest"` | `"vitest"` | Generated tests use Vitest instead of Jest |
- *
- * ## Migration Strategy
- *
- * This migration uses the nullish coalescing assignment operator (`??=`) to only set
- * values that are explicitly undefined. This means:
- * - ✅ If a user has explicitly configured a field, that value is preserved
- * - ✅ If a field is undefined, the old default is set
- * - ✅ Users can opt into modern tooling by removing these fields later
- *
- * ## Examples
- *
- * ### Example 1: Empty Config (Migration Applied - Keep Yarn + Jest)
- *
- * **Before Migration (2.9.0 → 3.0.0):**
- * ```yaml
- * generators:
- *   - name: fernapi/fern-typescript-sdk
- *     version: 2.9.0
- *     config: {}
- * ```
- *
- * **After Migration:**
- * ```yaml
- * generators:
- *   - name: fernapi/fern-typescript-sdk
- *     version: 3.0.0
- *     config:
- *       packageManager: yarn    # Set by migration - keeps yarn
- *       testFramework: jest     # Set by migration - keeps jest
- * ```
- *
- * **Result:** Generated SDK continues using yarn and Jest.
- *
- * **Generated Files:**
- * - `package.json` with yarn scripts and Jest config
- * - Test files using Jest syntax (`describe`, `it`, `expect`)
- * - `.yarnrc` or `.yarnrc.yml` if applicable
- *
- * ### Example 2: Adopting Modern Tooling (pnpm + Vitest)
- *
- * **After Initial Migration:**
- * ```yaml
- * generators:
- *   - name: fernapi/fern-typescript-sdk
- *     version: 3.0.0
- *     config:
- *       packageManager: yarn
- *       testFramework: jest
- * ```
- *
- * **To Adopt pnpm + Vitest:**
- * ```yaml
- * generators:
- *   - name: fernapi/fern-typescript-sdk
- *     version: 3.0.0
- *     config: {}  # Remove to use new defaults
- * ```
- *
- * **Result:** Generated SDK uses pnpm and Vitest.
- *
- * **Generated Files:**
- * - `package.json` with pnpm scripts
- * - `vitest.config.ts` for test configuration
- * - Test files using Vitest syntax (compatible with Jest)
- * - `pnpm-workspace.yaml` if applicable
- *
- * ### Example 3: Mixed Tooling (Custom Configuration)
- *
- * **Keep yarn but adopt Vitest:**
- * ```yaml
- * generators:
- *   - name: fernapi/fern-typescript-sdk
- *     version: 3.0.0
- *     config:
- *       packageManager: yarn    # Keep yarn
- *       # testFramework defaults to vitest
- * ```
- *
- * **Keep Jest but adopt pnpm:**
- * ```yaml
- * generators:
- *   - name: fernapi/fern-typescript-sdk
- *     version: 3.0.0
- *     config:
- *       testFramework: jest     # Keep Jest
- *       # packageManager defaults to pnpm
- * ```
- *
- * ## Why These Defaults Changed
- *
- * ### pnpm vs yarn
- *
- * **Performance:**
- * - pnpm install is 2-3x faster than yarn
- * - Uses hard links instead of copying files
- * - Significantly smaller `node_modules` (50-70% reduction)
- *
- * **Correctness:**
- * - Strict dependency resolution prevents phantom dependencies
- * - Better monorepo support with workspaces
- * - More deterministic builds
- *
- * **Ecosystem:**
- * - Growing adoption in major projects (Vue 3, Prisma, Turborepo)
- * - Better compatibility with modern tooling
- *
- * ### Vitest vs Jest
- *
- * **Performance:**
- * - 10-20x faster test execution with native ESM
- * - Built-in watch mode with instant HMR
- * - Parallel test execution by default
- *
- * **Developer Experience:**
- * - Native TypeScript support (no ts-jest needed)
- * - Vite-powered with instant module reloading
- * - Jest-compatible API (easy migration)
- * - Better error messages and stack traces
- *
- * **Modern Features:**
- * - Native ESM support
- * - Web Workers and multi-threading support
- * - In-source testing capabilities
- *
- * ## Compatibility Notes
- *
- * ### Vitest Limitations
- *
- * Vitest is **not compatible** with certain generator configurations:
- *
- * 1. **`useBigInt: true`**: Vitest doesn't handle BigInt serialization the same way as Jest
- *    - **Workaround**: Keep `testFramework: jest` if using BigInt
- *
- * 2. **`streamType: wrapper`**: Older stream wrappers may not work with Vitest's ESM mode
- *    - **Workaround**: Either use `streamType: web` or keep `testFramework: jest`
- *
- * 3. **`packagePath` (custom paths)**: May have module resolution issues with Vitest
- *    - **Workaround**: Keep `testFramework: jest` for complex custom paths
- *
- * If you have any of these configurations, the migration correctly keeps Jest as the test framework.
- *
- * ## Migration Path to Modern Tooling
- *
- * ### Step 1: Upgrade with Migration (Safe)
- * ```bash
- * fern generator upgrade
- * ```
- * Result: Keeps yarn and Jest, no workflow changes needed.
- *
- * ### Step 2: Install pnpm (Optional)
- * ```bash
- * npm install -g pnpm@latest
- * ```
- *
- * ### Step 3: Adopt Modern Tooling (Optional)
- * Edit `generators.yml`:
- * ```yaml
- * config: {}  # Use pnpm + vitest
- * ```
- *
- * ### Step 4: Update CI/CD (Optional)
- * Update CI scripts to use pnpm:
- * ```yaml
- * # GitHub Actions example
- * - uses: pnpm/action-setup@v2
- *   with:
- *     version: 8
- * - run: pnpm install
- * - run: pnpm test
- * ```
- *
- * ### Step 5: Migrate yarn.lock (Optional)
- * ```bash
- * # Convert yarn.lock to pnpm-lock.yaml
- * pnpm import
- * rm yarn.lock
- * ```
- *
- * ## Troubleshooting
- *
- * ### "pnpm: command not found"
- * **Cause:** pnpm not installed globally.
- * **Solution:** Install pnpm: `npm install -g pnpm`
- *
- * ### Vitest errors with BigInt
- * **Cause:** Vitest and BigInt serialization incompatibility.
- * **Solution:** Use `testFramework: jest` in config.
- *
- * ### Module resolution errors with Vitest
- * **Cause:** ESM/CommonJS compatibility issues.
- * **Solution:** Either fix module format or use `testFramework: jest`.
- *
- * ### Tests fail after switching to Vitest
- * **Cause:** Vitest has stricter ESM requirements.
- * **Solution:** Ensure `package.json` has `"type": "module"` or use `.ts` extensions.
- *
- * ## Performance Comparison
- *
- * Based on typical SDK project (50 tests, 1000 LOC):
- *
- * **Install Time:**
- * - yarn: ~15s
- * - pnpm: ~5s (3x faster)
- *
- * **Test Execution:**
- * - Jest: ~8s
- * - Vitest: ~0.8s (10x faster)
- *
- * **Disk Usage:**
- * - yarn: ~200MB node_modules
- * - pnpm: ~80MB node_modules (60% reduction)
- *
- * ## Recommendations
- *
- * - **New projects**: Use the new defaults (pnpm + Vitest)
- * - **Existing projects**: Keep old defaults initially, migrate when convenient
- * - **CI/CD-heavy projects**: Consider pnpm for faster installs
- * - **Projects with BigInt**: Keep Jest until Vitest improves BigInt support
- */
-export const migration_3_0_0 = {
-    version: "3.0.0",
-    migrateGeneratorConfig: ({ config }) => migrateConfig(config, (draft) => {
-        // Only set old defaults if the fields are not already explicitly configured
-        draft.packageManager ??= "yarn";
-        draft.testFramework ??= "jest";
-    }),
-    migrateGeneratorsYml: ({ document }) => document
-};
-//# sourceMappingURL=3.0.0.js.map

package/lib/generators/typescript/migrations/3.0.0.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"3.0.0.js","sourceRoot":"","sources":["../../../../src/generators/typescript/migrations/3.0.0.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,aAAa,EAAE,MAAM,2BAA2B,CAAC;AAE1D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8OG;AACH,MAAM,CAAC,MAAM,eAAe,GAAc;IACtC,OAAO,EAAE,OAAO;IAEhB,sBAAsB,EAAE,CAAC,EAAE,MAAM,EAAE,EAAE,EAAE,CACnC,aAAa,CAAC,MAAM,EAAE,CAAC,KAAK,EAAE,EAAE;QAC5B,4EAA4E;QAC5E,KAAK,CAAC,cAAc,KAAK,MAAM,CAAC;QAChC,KAAK,CAAC,aAAa,KAAK,MAAM,CAAC;IACnC,CAAC,CAAC;IAEN,oBAAoB,EAAE,CAAC,EAAE,QAAQ,EAAE,EAAE,EAAE,CAAC,QAAQ;CACnD,CAAC"}

package/lib/generators/typescript/migrations/index.d.ts

@@ -1,18 +0,0 @@
-import type { MigrationModule } from "@fern-api/migrations-base";
-/**
- * Migration module for TypeScript SDK generators.
- *
- * This module contains migrations for configuration changes across
- * all TypeScript SDK generator variants:
- * - fernapi/fern-typescript
- * - fernapi/fern-typescript-sdk
- * - fernapi/fern-typescript-node-sdk
- * - fernapi/fern-typescript-browser-sdk
- *
- * Each migration is defined in a separate file under this directory.
- * Migrations are automatically applied by the Fern CLI when running:
- * `fern generator upgrade --generator typescript-sdk`
- */
-declare const migrationModule: MigrationModule;
-export default migrationModule;
-//# sourceMappingURL=index.d.ts.map

package/lib/generators/typescript/migrations/index.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../src/generators/typescript/migrations/index.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,2BAA2B,CAAC;AAMjE;;;;;;;;;;;;;GAaG;AACH,QAAA,MAAM,eAAe,EAAE,eAEtB,CAAC;AAEF,eAAe,eAAe,CAAC"}

package/lib/generators/typescript/migrations/index.js

@@ -1,22 +0,0 @@
-import { migration_1_0_0 } from "./1.0.0.js";
-import { migration_2_0_0 } from "./2.0.0.js";
-import { migration_3_0_0 } from "./3.0.0.js";
-/**
- * Migration module for TypeScript SDK generators.
- *
- * This module contains migrations for configuration changes across
- * all TypeScript SDK generator variants:
- * - fernapi/fern-typescript
- * - fernapi/fern-typescript-sdk
- * - fernapi/fern-typescript-node-sdk
- * - fernapi/fern-typescript-browser-sdk
- *
- * Each migration is defined in a separate file under this directory.
- * Migrations are automatically applied by the Fern CLI when running:
- * `fern generator upgrade --generator typescript-sdk`
- */
-const migrationModule = {
-    migrations: [migration_1_0_0, migration_2_0_0, migration_3_0_0]
-};
-export default migrationModule;
-//# sourceMappingURL=index.js.map

package/lib/generators/typescript/migrations/index.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../../src/generators/typescript/migrations/index.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,eAAe,EAAE,MAAM,YAAY,CAAC;AAC7C,OAAO,EAAE,eAAe,EAAE,MAAM,YAAY,CAAC;AAC7C,OAAO,EAAE,eAAe,EAAE,MAAM,YAAY,CAAC;AAE7C;;;;;;;;;;;;;GAaG;AACH,MAAM,eAAe,GAAoB;IACrC,UAAU,EAAE,CAAC,eAAe,EAAE,eAAe,EAAE,eAAe,CAAC;CAClE,CAAC;AAEF,eAAe,eAAe,CAAC"}

package/lib/index.d.ts

@@ -1,18 +0,0 @@
-/**
- * @fern-api/generator-migrations
- *
- * Unified migration package for all Fern generator configurations.
- *
- * This package contains migrations for all generators, organized by generator name.
- */
-import type { MigrationModule } from "@fern-api/migrations-base";
-/**
- * All generator migrations indexed by full generator name.
- *
- * When adding migrations for a new generator:
- * 1. Add migrations under src/generators/{language}/migrations/
- * 2. Import the migration module
- * 3. Add entries for all generator name variants
- */
-export declare const migrations: Record<string, MigrationModule>;
-//# sourceMappingURL=index.d.ts.map

package/lib/index.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,2BAA2B,CAAC;AAGjE;;;;;;;GAOG;AACH,eAAO,MAAM,UAAU,EAAE,MAAM,CAAC,MAAM,EAAE,eAAe,CAMtD,CAAC"}

package/lib/index.js

@@ -1,24 +0,0 @@
-/**
- * @fern-api/generator-migrations
- *
- * Unified migration package for all Fern generator configurations.
- *
- * This package contains migrations for all generators, organized by generator name.
- */
-import typescriptSdkMigrations from "./generators/typescript/migrations/index.js";
-/**
- * All generator migrations indexed by full generator name.
- *
- * When adding migrations for a new generator:
- * 1. Add migrations under src/generators/{language}/migrations/
- * 2. Import the migration module
- * 3. Add entries for all generator name variants
- */
-export const migrations = {
-    // TypeScript SDK - all variants share the same migrations
-    "fernapi/fern-typescript": typescriptSdkMigrations,
-    "fernapi/fern-typescript-sdk": typescriptSdkMigrations,
-    "fernapi/fern-typescript-node-sdk": typescriptSdkMigrations,
-    "fernapi/fern-typescript-browser-sdk": typescriptSdkMigrations
-};
-//# sourceMappingURL=index.js.map

package/lib/index.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAGH,OAAO,uBAAuB,MAAM,6CAA6C,CAAC;AAElF;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,UAAU,GAAoC;IACvD,0DAA0D;IAC1D,yBAAyB,EAAE,uBAAuB;IAClD,6BAA6B,EAAE,uBAAuB;IACtD,kCAAkC,EAAE,uBAAuB;IAC3D,qCAAqC,EAAE,uBAAuB;CACjE,CAAC"}