target.ts overviewCopy Anchor Link

Exports Grouped by CategoryCopy Anchor Link

• utils
  • Imports
  • isTargetModuleSupported
  • moduleSpecifier
  • unsupportedModules

utilsCopy Anchor Link

ImportsCopy Anchor Link

Signature

declare const Imports: (_context?: GenerationContext) => {
  readonly core: "effect"
  readonly http: "effect/http"
  readonly httpApi: "effect/http-api"
  readonly net: "effect/net"
  readonly rpc: "effect/rpc"
  readonly cli: "effect/cli"
  readonly sql: "effect/sql"
}

isTargetModuleSupportedCopy Anchor Link

The pipeline checks source modules before rendering; imports remain a total pure projection.

Signature

declare const isTargetModuleSupported: (context: GenerationContext, module: string) => boolean

moduleSpecifierCopy Anchor Link

Map a generated import to the target installation. Explicit .ts paths point to generated siblings; extensionless local refs originated at the canonical source import base and must be rebased before choosing the target TypeScript extension policy.

Signature

declare const moduleSpecifier: (context: GenerationContext, module: string) => string

unsupportedModulesCopy Anchor Link

Collect unsupported app symbol modules, including those inside JSON extension payloads.

Signature

declare const unsupportedModules: (ir: ApplicationIR, context: GenerationContext) => ReadonlyArray<string>