// native-seam manifest — the canonical registry of upstream packages whose
// native-module spec files we override.
//
// the rule: when a guest bundle imports from one of these packages, vite lets
// the package's JS resolve from node_modules normally. only the listed
// `seamBasenames` are redirected to our stub. this keeps the upstream JS layer
// (hooks, helpers, transforms, listeners) running unchanged.
//
// adding a new entry:
//   1. identify upstream's native-module file (look for files calling
//      `requireNativeModule`, `TurboModuleRegistry.getEnforced`,
//      `requireNativeComponent`, or in `src/specs/Native*Module.ts`)
//   2. write a thin stub at `packages/compat/src/stubs/native-seams/<pkg>.ts`
//      that exports the same default + named exports upstream's seam file
//      exports — except the implementation calls into sootsim's engine.
//   3. append an entry below. the plugin handles the rest.
//
// canonical example: react-native-reanimated. see
//   - `packages/compat/src/stubs/react-native-reanimated.ts` (the seam stub)
//   - `reanimatedNativeSeamRedirect` in vite-plugin.ts (still hard-coded
//     because it has package-specific edge cases — fabricUtils,
//     validate-worklets-version. new entries should use this manifest path
//     for the simple basename-match case.)

export interface NativeSeamEntry {
  /**
   * upstream npm package name. all imports whose importer path includes
   * `/<pkg>/` are candidates for redirect.
   */
  pkg: string
  /**
   * basenames of upstream files to redirect. each entry matches the file
   * name (no extension, no platform suffix like `.ios` / `.android`) of any
   * upstream module imported transitively from within `pkg`.
   *
   * example: if upstream has
   * `node_modules/expo-notifications/src/NotificationsHandler.ts`, list
   * `'NotificationsHandler'` here and we'll redirect any import resolving
   * to that file to our seam stub.
   */
  seamBasenames: string[]
  /**
   * absolute path to the seam stub. typically
   * `packages/compat/src/stubs/native-seams/<pkg>.ts` — but a single stub
   * file may export every native module the package exposes, so the same
   * `target` can appear in multiple entries if a package has multiple native
   * modules that share an implementation file.
   *
   * authors set this via the `seamPath(<pkg>)` helper below.
   */
  target: string
  /**
   * notes — short reason this entry exists. shown by the debug logger when
   * `SOOTSIM_NATIVE_SEAM_DEBUG=1` is set.
   */
  notes?: string
}

import fs from 'node:fs'
import path from 'node:path'
import { fileURLToPath } from 'node:url'

const HERE = path.dirname(fileURLToPath(import.meta.url))
const NATIVE_SEAMS_DIR = path.resolve(HERE, '../../compat/src/stubs/native-seams')

/** resolve a stub path under `packages/compat/src/stubs/native-seams/`.
 * resolves to `.tsx` when only that exists (JSX-bearing seams like
 * expo-image, react-native-webview). preferred order: `.ts`, `.tsx`. */
export function seamPath(basename: string): string {
  const ts = path.resolve(NATIVE_SEAMS_DIR, `${basename}.ts`)
  if (fs.existsSync(ts)) return ts
  const tsx = path.resolve(NATIVE_SEAMS_DIR, `${basename}.tsx`)
  if (fs.existsSync(tsx)) return tsx
  // fall through to .ts so vite's "Could not load" error names the .ts
  // path the author probably intended to create, instead of silently
  // pointing at something that doesn't exist with no extension.
  return ts
}

/**
 * the manifest. agents append entries here during the native-seam migration
 * (plans/sootsim/compat/compat-stubs-native-seam-audit.md). keep alphabetical by `pkg` to
 * minimise merge conflicts.
 */
export const NATIVE_SEAM_MANIFEST: NativeSeamEntry[] = [
  // entries land here during the Phase 1 migration. example shape:
  //
  // {
  //   pkg: 'expo-notifications',
  //   seamBasenames: [
  //     'NotificationsHandler',
  //     'NotificationsEmitter',
  //     'NotificationScheduler',
  //     'NotificationCategoriesService',
  //     'ServerRegistrationModule',
  //   ],
  //   target: seamPath('expo-notifications'),
  //   notes: 'route through engine NotificationBus',
  // },
  {
    pkg: '@metamask/react-native-search-api',
    // upstream is single-file `index.js`; no sub-imports inside the package
    // to redirect at the basename layer. listed here for documentation parity
    // — the bundle-loader's stub-registry routes the package-entry directly to
    // `stubs/metamask-react-native-search-api.ts`, which pairs the upstream
    // JS wrapper with the native seam below.
    seamBasenames: ['index'],
    target: seamPath('metamask-react-native-search-api'),
    notes:
      'iOS CoreSpotlight + NSUserActivity native seam; pure-JS wrapper class lives at stubs/metamask-react-native-search-api.ts',
  },
  {
    pkg: '@ua/react-native-airship',
    seamBasenames: [
      // src/NativeRNAirship.ts — the RNAirship TurboModule
      'NativeRNAirship',
      // codegen host components (no native backing in sootsim)
      'RNAirshipEmbeddedViewNativeComponent',
      'RNAirshipMessageViewNativeComponent',
    ],
    target: seamPath('react-native-airship'),
    notes:
      'push-notification SAAS — noop the SAAS layer, route banners through NotificationBus',
  },
  {
    pkg: 'react-native-background-fetch',
    // src/NativeBackgroundFetch.ts — TurboModuleRegistry.getEnforcing('RNBackgroundFetch')
    seamBasenames: ['NativeBackgroundFetch'],
    target: seamPath('react-native-background-fetch'),
    notes:
      'iOS BGTaskScheduler / Android WorkManager TurboModule — no real scheduler in browser; acknowledge registrations, never fire periodic events',
  },
  {
    pkg: 'expo-apple-authentication',
    // src/ExpoAppleAuthenticationButton.ts is the package's native-view
    // boundary. direct-compiled apps do not run the fetched-bundle lazy seam
    // loader, so route that boundary to the same view manager implementation.
    seamBasenames: ['ExpoAppleAuthenticationButton'],
    target: seamPath('expo-apple-authentication-view'),
    notes:
      'ASAuthorizationAppleIDButton native view — render the system button surface while upstream AppleAuthenticationButton.tsx remains unchanged',
  },
  {
    pkg: 'expo-asset',
    // src/ExpoAsset.ts — `requireNativeModule('ExpoAsset')`; only
    // `downloadAsync` is on the native surface. all the rest (`Asset`,
    // `AssetHooks`, `AssetSourceResolver`, ...) is pure JS that composes on
    // top.
    seamBasenames: ['ExpoAsset'],
    target: seamPath('expo-asset'),
    notes:
      'expo-modules-core requireNativeModule(ExpoAsset) — only downloadAsync; mirror upstream web build (return remote URL)',
  },
  {
    pkg: '@bam.tech/react-native-image-resizer',
    // upstream is not shipped to most guest bundles via node_modules — it
    // arrives through the bundle-loader stub-registry which routes the
    // package entry to `stubs/bam-react-native-image-resizer.ts`. listed here
    // for documentation parity; vite-path redirect would key on
    // `NativeImageResizer`.
    seamBasenames: ['NativeImageResizer'],
    target: seamPath('bam-react-native-image-resizer'),
    notes:
      'ImageResizer TurboModule — browser-side canvas resize implementing the iOS contain/cover/stretch + onlyScaleDown semantics from ios/ImageResizer.mm',
  },
  {
    pkg: 'react-native-adjust',
    // upstream's `index.js` reads `NativeModules.Adjust` and
    // `NativeModules.AdjustEventEmitter` directly — there is no NativeAdjust
    // spec file. listed for documentation parity; the actual seam delivery is
    // through the bundle-loader stub-registry routing the package entry to
    // `stubs/react-native-adjust.ts`, which imports the native seam from this
    // target.
    seamBasenames: ['index'],
    target: seamPath('react-native-adjust'),
    notes:
      'Adjust attribution SAAS — noop native side (Adjust + AdjustEventEmitter NativeModules), pure-JS classes (AdjustConfig/AdjustEvent/...) live in stubs/react-native-adjust.ts',
  },
  {
    pkg: 'expo-clipboard',
    // src/ExpoClipboard.ts — `requireNativeModule<ExpoClipboardModule>('ExpoClipboard')`.
    // upstream also ships `ExpoClipboard.web.ts` (which we mirror); the
    // redirect catches both `.ts` and `.web.ts` since basenames match.
    seamBasenames: ['ExpoClipboard'],
    target: seamPath('expo-clipboard'),
    notes:
      'expo-modules-core requireNativeModule(ExpoClipboard) — real navigator.clipboard text + ClipboardItem image; mirrors upstream ExpoClipboard.web.ts',
  },
  {
    pkg: 'expo-font',
    // src/ExpoFontLoader.ts — `requireNativeModule<ExpoFontLoaderModule>('ExpoFontLoader')`.
    // we mirror upstream's web variant `ExpoFontLoader.web.ts` (FontFace API
    // + managed <style id="expo-generated-fonts">).
    seamBasenames: ['ExpoFontLoader'],
    target: seamPath('expo-font'),
    notes:
      'expo-modules-core requireNativeModule(ExpoFontLoader) — FontFace API registration; mirrors upstream ExpoFontLoader.web.ts',
  },
  {
    pkg: '@react-native-async-storage/async-storage',
    // src/NativeAsyncStorageModule.ts — TurboModule spec for `RNCAsyncStorage`.
    // src/RCTAsyncStorage.ts — legacy `NativeModules['RNCAsyncStorage']` resolver.
    // both basenames redirect to the same seam; upstream's AsyncStorage.ts
    // imports default from either depending on bridgeless vs paper.
    seamBasenames: ['NativeAsyncStorageModule', 'RCTAsyncStorage'],
    target: seamPath('async-storage'),
    notes:
      'RNCAsyncStorage TurboModule — localStorage-backed; preserves multiMerge JSON deep-merge semantics from upstream iOS module',
  },
  // expo-calendar and expo-contacts deliberately have NO entry here. expo
  // renamed their native module ids across majors (`ExpoCalendar` →
  // `CalendarNext`, `ExpoContacts` → `ExpoContactsNext`) and kept the old
  // ids serving the `/legacy` subpath, so one package now asks for two
  // different native modules depending on which entry point you import.
  // basename matching cannot tell `src/ExpoCalendar.ts` from
  // `src/legacy/ExpoCalendar.ts`, so a redirect here forces the legacy API
  // onto the class-based seam, whose methods throw.
  //
  // registering by module NAME instead is what keeps old and new package
  // versions both working: ../../compat/src/stubs/expo-{calendar,contacts}-register.ts
  // installs every id either version asks for, and upstream's own
  // `requireNativeModule` picks the right one per entry point. a file
  // redirect can only match one layout, so it breaks the versions it was
  // not written for.
  {
    pkg: 'expo-media-library',
    // src/ExpoMediaLibrary.ts — `requireNativeModule('ExpoMediaLibrary')`.
    // seam mirrors upstream's `ExpoMediaLibrary.web.ts` (refuse permissions
    // + expose MediaType/SortBy constants).
    seamBasenames: ['ExpoMediaLibrary'],
    target: seamPath('expo-media-library'),
    notes:
      'expo-modules-core requireNativeModule(ExpoMediaLibrary) — refuses permissions + exposes MediaType/SortBy enums per upstream ExpoMediaLibrary.web.ts',
  },
  {
    pkg: 'expo-file-system',
    // src/ExpoFileSystem.ts — `requireNativeModule('ExpoFileSystem')`. seam
    // mirrors upstream's `ExpoFileSystem.web.ts` (warn-not-supported stubs).
    seamBasenames: ['ExpoFileSystem'],
    target: seamPath('expo-file-system'),
    notes:
      'expo-modules-core requireNativeModule(ExpoFileSystem) — warn-not-supported stubs per upstream ExpoFileSystem.web.ts; no general browser fs access',
  },
  {
    pkg: 'expo-image-picker',
    // src/ExponentImagePicker.ts — `requireNativeModule('ExponentImagePicker')`.
    // seam routes selection requests through sootsim's engine-owned image
    // picker (`SootSim.bridges.imagePicker.pickFromLibrary`) so the same
    // canvas-rendered iOS picker handles every image-source library.
    seamBasenames: ['ExponentImagePicker'],
    target: seamPath('expo-image-picker'),
    notes:
      "expo-modules-core requireNativeModule(ExponentImagePicker) — routes through engine SootSim.bridges.imagePicker (shell-worker ImagePickerView) instead of upstream web build's DOM <input type=file>",
  },
  {
    pkg: 'expo-camera',
    // upstream splits the native surface across two files:
    //   - src/ExpoCamera.ts        → requireNativeViewManager('ExpoCamera')
    //   - src/ExpoCameraManager.ts → requireNativeModule('ExpoCamera')
    // each basename redirects to a different seam — the view component vs.
    // the imperative module. live preview + capture route through the same
    // engine `camera-stream` module the built-in sootsim Camera app uses,
    // so guest <CameraView> sees the same feed as the OS camera app.
    seamBasenames: ['ExpoCamera'],
    target: seamPath('expo-camera'),
    notes:
      'expo-camera native view manager — host component backed by engine camera-stream (same getUserMedia pipeline as the built-in CameraApp); exposes CameraViewRef methods (takePicture/...) via useImperativeHandle',
  },
  {
    pkg: 'expo-camera',
    seamBasenames: ['ExpoCameraManager'],
    target: seamPath('expo-camera-manager'),
    notes:
      'expo-camera native module — permissions/feature-gates/codecs/Type/FlashMode constants; barcode scanner is noop (no engine scanner integration)',
  },
  {
    pkg: 'expo-image',
    // upstream splits the native surface across two files:
    //   - src/ExpoImage.tsx → requireNativeViewManager('ExpoImage')
    //   - src/ImageModule.ts → requireNativeModule('ExpoImage')
    // the view-component seam translates expo-image's prop shape
    // (contentFit, tintColor, source) onto sootsim's existing
    // <sootsim-image> host. no new canvas component is needed — sootsim's
    // image-loader + canvaskit-renderer already handle resizeMode,
    // tintColor, and onLoad/onError lifecycle.
    seamBasenames: ['ExpoImage'],
    target: seamPath('expo-image'),
    notes:
      'expo-image native view — thin prop translator onto sootsim-image host (contentFit→resizeMode, tintColor passthrough); upstream Image.tsx + ImageBackground + useImage resolve from node_modules unchanged',
  },
  {
    pkg: 'expo-image',
    seamBasenames: ['ImageModule'],
    target: seamPath('expo-image-module'),
    notes:
      'expo-image native module — prefetch/loadAsync route through sootsim image-loader; cache controls noop (browser owns HTTP cache); blurhash encode not yet implemented',
  },
  {
    pkg: '@notifee/react-native',
    // src/NotifeeNativeModule.ts — the base class NotifeeApiModule extends.
    // upstream also ships .web.ts (returns `{}` from `native`); both
    // basenames redirect to the same seam — a real implementation that
    // routes `this.native.*` calls through the engine NotificationBus.
    seamBasenames: ['NotifeeNativeModule'],
    target: seamPath('notifee'),
    notes:
      'Notifee NotifeeApiModule base class — routes display/cancel/channel/badge calls through engine NotificationBus; tap events fan out via the shared NotifeeJSEventEmitter so onForegroundEvent listeners fire',
  },
  {
    pkg: 'expo-notifications',
    // five native module spec files, each `requireNativeModule(...)`-shaped.
    // every one redirects to the same `expo-notifications` seam — see
    // `stubs/native-seams/expo-notifications.ts` for the union surface.
    seamBasenames: [
      // src/NotificationsHandlerModule.ts — presentation policy
      'NotificationsHandlerModule',
      // src/NotificationsEmitterModule.ts — last-tap response + listener
      'NotificationsEmitterModule',
      // src/NotificationScheduler.ts — schedule / cancel
      'NotificationScheduler',
      // src/BadgeModule.ts — app badge count
      'BadgeModule',
      // src/ServerRegistrationModule.ts — expo push registration
      'ServerRegistrationModule',
    ],
    target: seamPath('expo-notifications'),
    notes:
      'expo-notifications native modules — routes scheduling/badge/installation-id through engine NotificationBus; tap callbacks fan out via the bus event emitters',
  },
  {
    pkg: 'react-native-enriched-markdown',
    seamBasenames: [
      'EnrichedMarkdownTextNativeComponent',
      'EnrichedMarkdownNativeComponent',
      'EnrichedMarkdownTextInputNativeComponent',
    ],
    target: seamPath('react-native-enriched-markdown'),
    notes:
      'generated Fabric markdown host components; upstream Streamdown/enriched-markdown JS runs unchanged',
  },
]