@ttsc/unplugin 0.16.3 → 0.16.4

package/README.md

@@ -122,7 +122,7 @@ export default withTtsc(nextConfig);
 
 ### Turbopack
 
-Turbopack has no JS plugin API, but it runs webpack loaders through `turbopack.rules` — and a ttsc transform is exactly loader-shaped (TypeScript source in, transformed source out). `@ttsc/unplugin/turbopack` is that standalone loader:
+Turbopack has no JS plugin API, but it runs webpack loaders through `turbopack.rules`, and a ttsc transform is exactly loader-shaped (TypeScript source in, transformed source out). `@ttsc/unplugin/turbopack` is that standalone loader:
 
 ```js
 // next.config.mjs
@@ -280,7 +280,7 @@ Supported entrypoints are:
 - `@ttsc/unplugin/next`
 - `@ttsc/unplugin/bun`
 
-Each entrypoint supports ESM import and CJS require. In CommonJS configs, read the default export from `require("@ttsc/unplugin/vite").default`. `@ttsc/unplugin/turbopack` is not an unplugin factory but a standalone webpack loader — reference it by module name inside `turbopack.rules` instead of calling it.
+Each entrypoint supports ESM import and CJS require. In CommonJS configs, read the default export from `require("@ttsc/unplugin/vite").default`. `@ttsc/unplugin/turbopack` is not an unplugin factory but a standalone webpack loader; reference it by module name inside `turbopack.rules` instead of calling it.
 
 ### Options
 
@@ -302,7 +302,7 @@ const options: TtscUnpluginOptions = {
 
 ### Watch Mode and HMR
 
-Transform plugins may report, per file, the source files they consulted (the transform envelope's `dependencies` field — see the [plugin protocol](https://ttsc.dev/docs/development/concepts/protocol#transform)). The adapter registers each reported path with the bundler via `addWatchFile`, so editing a type that only a generated validator depends on invalidates the module in watch mode even though the bundler erased the type-only import from its graph.
+Transform plugins may report, per file, the source files they consulted (the transform envelope's `dependencies` field, see the [plugin protocol](https://ttsc.dev/docs/development/concepts/protocol#transform)). The adapter registers each reported path with the bundler via `addWatchFile`, so editing a type that only a generated validator depends on invalidates the module in watch mode even though the bundler erased the type-only import from its graph.
 
 ## Sponsors
 

package/lib/core/index.js

@@ -16,7 +16,7 @@ const sourceFilePattern = /\.[cm]?tsx?$/;
 /** Matches any path segment that is a `node_modules` directory (cross-platform). */
 const nodeModulesPattern = /(?:^|[/\\])node_modules(?:[/\\]|$)/;
 /**
- * Matches virtual module ids — Rollup/Vite use a leading NUL byte (`\0`) as
+ * Matches virtual module ids: Rollup/Vite use a leading NUL byte (`\0`) as
  * convention.
  */
 const virtualModulePattern = /\0/;

package/lib/core/index.mjs

@@ -12,7 +12,7 @@ const sourceFilePattern = /\.[cm]?tsx?$/;
 /** Matches any path segment that is a `node_modules` directory (cross-platform). */
 const nodeModulesPattern = /(?:^|[/\\])node_modules(?:[/\\]|$)/;
 /**
- * Matches virtual module ids — Rollup/Vite use a leading NUL byte (`\0`) as
+ * Matches virtual module ids: Rollup/Vite use a leading NUL byte (`\0`) as
  * convention.
  */
 const virtualModulePattern = /\0/;

package/lib/core/options.d.ts

@@ -30,8 +30,8 @@ export interface TtscUnpluginOptions {
  * Fully-resolved plugin options with all defaults applied.
  *
  * Produced by {@link resolveOptions}; consumed internally by the transform
- * pipeline. Every field is present and normalised — callers should not
- * construct this type directly.
+ * pipeline. Every field is present and normalised; callers should not construct
+ * this type directly.
  */
 export interface ResolvedTtscUnpluginOptions {
     /** Compiler-options overlay applied on top of the discovered tsconfig. */

package/lib/core/transform.d.ts

@@ -27,7 +27,7 @@ export interface TtscTransformAlias {
  * input file. On subsequent transforms the cached entry is validated by
  * re-hashing the project and comparing against {@link inputHashes}; a mismatch
  * triggers a full re-transform. Both sides hash the same set of files (the
- * project directory walk), so the comparison is meaningful — keying the
+ * project directory walk), so the comparison is meaningful; keying the
  * compiler's out-of-walk output paths on only one side is what made the cache
  * miss on every module.
  */
@@ -85,7 +85,7 @@ export interface TtscTransformHooks {
  * @param cache - Optional per-build cache; cleared by the caller on
  *   `buildStart`.
  * @param hooks - Optional adapter callbacks; see {@link TtscTransformHooks}.
- *   Dependency notifications fire on cache hits too — watch registrations are
+ *   Dependency notifications fire on cache hits too; watch registrations are
  *   per build, not per compilation.
  */
 export declare function transformTtsc(id: string, source: string, options: ResolvedTtscUnpluginOptions, aliases?: unknown, cache?: TtscTransformCache, hooks?: TtscTransformHooks): Promise<TtscTransformResult | undefined>;

package/lib/core/transform.js

@@ -31,7 +31,7 @@ function createTtscTransformCache() {
  * @param cache - Optional per-build cache; cleared by the caller on
  *   `buildStart`.
  * @param hooks - Optional adapter callbacks; see {@link TtscTransformHooks}.
- *   Dependency notifications fire on cache hits too — watch registrations are
+ *   Dependency notifications fire on cache hits too; watch registrations are
  *   per build, not per compilation.
  */
 async function transformTtsc(id, source, options, aliases, cache, hooks) {
@@ -98,7 +98,7 @@ async function transformTtsc(id, source, options, aliases, cache, hooks) {
  * The transform envelope's `dependencies` keys mirror the `typescript` keys
  * (project-relative); values may be project-relative or absolute. Every path is
  * absolutized against the project root and deduplicated, and the file itself is
- * dropped — the bundler already watches the module it transforms.
+ * dropped; the bundler already watches the module it transforms.
  */
 function notifyFileDependencies(hooks, props) {
     const addWatchFile = hooks?.addWatchFile;
@@ -196,9 +196,9 @@ function createTransformResult(source, code) {
  *
  * Re-hashes every file under the project root and overlays the current module's
  * in-memory source, then compares the snapshot against the one captured when
- * the result was produced. Any input under the project root changing — the
- * module itself or a sibling the plugin reads — invalidates the entry and
- * forces a re-transform. Out-of-walk inputs a plugin pulls in (`node_modules`
+ * the result was produced. Any input under the project root changing (the
+ * module itself or a sibling the plugin reads) invalidates the entry and forces
+ * a re-transform. Out-of-walk inputs a plugin pulls in (`node_modules`
  * declarations, sibling-package sources) are not seen here; adapters invalidate
  * on those through the reported `dependencies` → `addWatchFile` → the bundler's
  * next `buildStart` cache clear.
@@ -208,8 +208,8 @@ function createTransformResult(source, code) {
  * the key universe. The earlier implementation overlaid the compiler's output
  * keys here on only one side; those keys include out-of-walk program inputs
  * (`node_modules` declarations, sibling-package sources), so the snapshots
- * never matched and the cache missed on every module — re-transforming the
- * whole project once per file on any project that imports a typed dependency.
+ * never matched and the cache missed on every module; re-transforming the whole
+ * project once per file on any project that imports a typed dependency.
  */
 function matchesCachedSource(cached, file, source) {
     const currentKey = toProjectKey(cached.projectRoot, file);
@@ -220,8 +220,8 @@ function matchesCachedSource(cached, file, source) {
 /**
  * Build the input-hash snapshot stored alongside a fresh compiler result.
  *
- * Hashes every file under the project directory — the exact universe
- * {@link matchesCachedSource} re-hashes to validate — then overlays the
+ * Hashes every file under the project directory (the exact universe
+ * {@link matchesCachedSource} re-hashes to validate), then overlays the
  * in-memory source for the module that triggered the compile so unsaved editor
  * content is captured correctly.
  *
@@ -419,7 +419,7 @@ function normalizePluginConfigForGeneratedTsconfig(entry, tsconfigDir) {
  * project's own `paths` wholesale. The overlay therefore re-states the
  * project's effective mappings first, so tsconfig-only aliases keep resolving;
  * inline `compilerOptions.paths` from the plugin options ride on top, and the
- * bundler aliases win last — they mirror what the bundler will actually do at
+ * bundler aliases win last; they mirror what the bundler will actually do at
  * resolve time.
  *
  * No `baseUrl` is emitted: TypeScript-Go removed the option (TS5102), and all
@@ -624,7 +624,7 @@ function formatUnknownError(error) {
  * If `tsconfig` is supplied it is returned as-is (absolute) or resolved from
  * `process.cwd()` (relative). Otherwise the function walks ancestor directories
  * starting at `file`'s directory, returning the first `tsconfig.json` found.
- * Falls back to `<cwd>/tsconfig.json` when no ancestor contains one — the
+ * Falls back to `<cwd>/tsconfig.json` when no ancestor contains one; the
  * compiler will error if that file does not exist, which is the correct
  * behavior for a mis-configured project.
  */
@@ -641,7 +641,7 @@ function resolveTsconfig(file, tsconfig) {
             return candidate;
         }
         const parent = path.dirname(current);
-        // Reached filesystem root — stop walking.
+        // Reached filesystem root, stop walking.
         if (parent === current) {
             break;
         }

package/lib/core/transform.mjs

@@ -29,7 +29,7 @@ function createTtscTransformCache() {
  * @param cache - Optional per-build cache; cleared by the caller on
  *   `buildStart`.
  * @param hooks - Optional adapter callbacks; see {@link TtscTransformHooks}.
- *   Dependency notifications fire on cache hits too — watch registrations are
+ *   Dependency notifications fire on cache hits too; watch registrations are
  *   per build, not per compilation.
  */
 async function transformTtsc(id, source, options, aliases, cache, hooks) {
@@ -96,7 +96,7 @@ async function transformTtsc(id, source, options, aliases, cache, hooks) {
  * The transform envelope's `dependencies` keys mirror the `typescript` keys
  * (project-relative); values may be project-relative or absolute. Every path is
  * absolutized against the project root and deduplicated, and the file itself is
- * dropped — the bundler already watches the module it transforms.
+ * dropped; the bundler already watches the module it transforms.
  */
 function notifyFileDependencies(hooks, props) {
     const addWatchFile = hooks?.addWatchFile;
@@ -194,9 +194,9 @@ function createTransformResult(source, code) {
  *
  * Re-hashes every file under the project root and overlays the current module's
  * in-memory source, then compares the snapshot against the one captured when
- * the result was produced. Any input under the project root changing — the
- * module itself or a sibling the plugin reads — invalidates the entry and
- * forces a re-transform. Out-of-walk inputs a plugin pulls in (`node_modules`
+ * the result was produced. Any input under the project root changing (the
+ * module itself or a sibling the plugin reads) invalidates the entry and forces
+ * a re-transform. Out-of-walk inputs a plugin pulls in (`node_modules`
  * declarations, sibling-package sources) are not seen here; adapters invalidate
  * on those through the reported `dependencies` → `addWatchFile` → the bundler's
  * next `buildStart` cache clear.
@@ -206,8 +206,8 @@ function createTransformResult(source, code) {
  * the key universe. The earlier implementation overlaid the compiler's output
  * keys here on only one side; those keys include out-of-walk program inputs
  * (`node_modules` declarations, sibling-package sources), so the snapshots
- * never matched and the cache missed on every module — re-transforming the
- * whole project once per file on any project that imports a typed dependency.
+ * never matched and the cache missed on every module; re-transforming the whole
+ * project once per file on any project that imports a typed dependency.
  */
 function matchesCachedSource(cached, file, source) {
     const currentKey = toProjectKey(cached.projectRoot, file);
@@ -218,8 +218,8 @@ function matchesCachedSource(cached, file, source) {
 /**
  * Build the input-hash snapshot stored alongside a fresh compiler result.
  *
- * Hashes every file under the project directory — the exact universe
- * {@link matchesCachedSource} re-hashes to validate — then overlays the
+ * Hashes every file under the project directory (the exact universe
+ * {@link matchesCachedSource} re-hashes to validate), then overlays the
  * in-memory source for the module that triggered the compile so unsaved editor
  * content is captured correctly.
  *
@@ -417,7 +417,7 @@ function normalizePluginConfigForGeneratedTsconfig(entry, tsconfigDir) {
  * project's own `paths` wholesale. The overlay therefore re-states the
  * project's effective mappings first, so tsconfig-only aliases keep resolving;
  * inline `compilerOptions.paths` from the plugin options ride on top, and the
- * bundler aliases win last — they mirror what the bundler will actually do at
+ * bundler aliases win last; they mirror what the bundler will actually do at
  * resolve time.
  *
  * No `baseUrl` is emitted: TypeScript-Go removed the option (TS5102), and all
@@ -622,7 +622,7 @@ function formatUnknownError(error) {
  * If `tsconfig` is supplied it is returned as-is (absolute) or resolved from
  * `process.cwd()` (relative). Otherwise the function walks ancestor directories
  * starting at `file`'s directory, returning the first `tsconfig.json` found.
- * Falls back to `<cwd>/tsconfig.json` when no ancestor contains one — the
+ * Falls back to `<cwd>/tsconfig.json` when no ancestor contains one; the
  * compiler will error if that file does not exist, which is the correct
  * behavior for a mis-configured project.
  */
@@ -639,7 +639,7 @@ function resolveTsconfig(file, tsconfig) {
             return candidate;
         }
         const parent = path.dirname(current);
-        // Reached filesystem root — stop walking.
+        // Reached filesystem root, stop walking.
         if (parent === current) {
             break;
         }

package/lib/core/tsconfigPaths.d.ts

@@ -6,8 +6,8 @@
  * is the whole object from the nearest config in the chain that declares one
  * (own config first, then `extends` entries in reverse priority order).
  * Relative targets are anchored at the directory of the config that declares
- * them — TypeScript-Go resolves inherited relative `paths` against the
- * declaring file, not the extending one.
+ * them. TypeScript-Go resolves inherited relative `paths` against the declaring
+ * file, not the extending one.
  *
  * The generated transform tsconfig replaces `paths` wholesale (standard
  * `extends` semantics), so the alias overlay must re-state these base mappings

package/lib/core/tsconfigPaths.js

@@ -12,8 +12,8 @@ var path = require('node:path');
  * is the whole object from the nearest config in the chain that declares one
  * (own config first, then `extends` entries in reverse priority order).
  * Relative targets are anchored at the directory of the config that declares
- * them — TypeScript-Go resolves inherited relative `paths` against the
- * declaring file, not the extending one.
+ * them. TypeScript-Go resolves inherited relative `paths` against the declaring
+ * file, not the extending one.
  *
  * The generated transform tsconfig replaces `paths` wholesale (standard
  * `extends` semantics), so the alias overlay must re-state these base mappings
@@ -59,7 +59,7 @@ function absolutizePathsTarget(baseDir, target) {
 /**
  * Locate the nearest `compilerOptions.paths` declaration in the `extends` chain
  * rooted at `tsconfig`. The own config wins over its bases; within an `extends`
- * array, later entries win over earlier ones. `seen` breaks circular chains —
+ * array, later entries win over earlier ones. `seen` breaks circular chains;
  * the compiler reports the actual config error.
  */
 function findDeclaredPaths(tsconfig, seen) {
@@ -111,7 +111,7 @@ function extendsSpecifiers(extended) {
  * Resolve an `extends` specifier to an absolute config path using TypeScript's
  * rules: absolute paths and relative specifiers get `.json` /
  * `tsconfig.json`-directory fallbacks; bare specifiers go through Node's module
- * resolver scoped to the declaring config. Returns `null` instead of throwing —
+ * resolver scoped to the declaring config. Returns `null` instead of throwing;
  * the compiler reports unresolvable `extends` itself.
  */
 function resolveExtendsConfig(tsconfig, specifier) {
@@ -176,7 +176,7 @@ function resolveRealPath(location) {
 }
 /**
  * Parse a JSONC (JSON with Comments) string by stripping comments and trailing
- * commas before handing off to `JSON.parse`. A leading UTF-8 BOM is dropped —
+ * commas before handing off to `JSON.parse`. A leading UTF-8 BOM is dropped;
  * `JSON.parse` rejects it, and this reader must not lose `paths` for a config
  * the compiler accepts.
  */

package/lib/core/tsconfigPaths.mjs

@@ -10,8 +10,8 @@ import path from 'node:path';
  * is the whole object from the nearest config in the chain that declares one
  * (own config first, then `extends` entries in reverse priority order).
  * Relative targets are anchored at the directory of the config that declares
- * them — TypeScript-Go resolves inherited relative `paths` against the
- * declaring file, not the extending one.
+ * them. TypeScript-Go resolves inherited relative `paths` against the declaring
+ * file, not the extending one.
  *
  * The generated transform tsconfig replaces `paths` wholesale (standard
  * `extends` semantics), so the alias overlay must re-state these base mappings
@@ -57,7 +57,7 @@ function absolutizePathsTarget(baseDir, target) {
 /**
  * Locate the nearest `compilerOptions.paths` declaration in the `extends` chain
  * rooted at `tsconfig`. The own config wins over its bases; within an `extends`
- * array, later entries win over earlier ones. `seen` breaks circular chains —
+ * array, later entries win over earlier ones. `seen` breaks circular chains;
  * the compiler reports the actual config error.
  */
 function findDeclaredPaths(tsconfig, seen) {
@@ -109,7 +109,7 @@ function extendsSpecifiers(extended) {
  * Resolve an `extends` specifier to an absolute config path using TypeScript's
  * rules: absolute paths and relative specifiers get `.json` /
  * `tsconfig.json`-directory fallbacks; bare specifiers go through Node's module
- * resolver scoped to the declaring config. Returns `null` instead of throwing —
+ * resolver scoped to the declaring config. Returns `null` instead of throwing;
  * the compiler reports unresolvable `extends` itself.
  */
 function resolveExtendsConfig(tsconfig, specifier) {
@@ -174,7 +174,7 @@ function resolveRealPath(location) {
 }
 /**
  * Parse a JSONC (JSON with Comments) string by stripping comments and trailing
- * commas before handing off to `JSON.parse`. A leading UTF-8 BOM is dropped —
+ * commas before handing off to `JSON.parse`. A leading UTF-8 BOM is dropped;
  * `JSON.parse` rejects it, and this reader must not lose `paths` for a config
  * the compiler accepts.
  */

package/lib/index.d.ts

@@ -1,5 +1,5 @@
 /**
- * @ttsc/unplugin — bundler-agnostic ttsc plugin adapter.
+ * @ttsc/unplugin: bundler-agnostic ttsc plugin adapter.
  *
  * Re-exports the unified `unplugin` instance that carries named bundler
  * adapters (`.vite`, `.rollup`, `.rolldown`, `.webpack`, `.rspack`, `.esbuild`,

package/lib/index.js

@@ -5,7 +5,7 @@ Object.defineProperty(exports, '__esModule', { value: true });
 var index = require('./core/index.js');
 
 /**
- * @ttsc/unplugin — bundler-agnostic ttsc plugin adapter.
+ * @ttsc/unplugin: bundler-agnostic ttsc plugin adapter.
  *
  * Re-exports the unified `unplugin` instance that carries named bundler
  * adapters (`.vite`, `.rollup`, `.rolldown`, `.webpack`, `.rspack`, `.esbuild`,

package/lib/index.mjs

@@ -1,7 +1,7 @@
 import unplugin from './core/index.mjs';
 
 /**
- * @ttsc/unplugin — bundler-agnostic ttsc plugin adapter.
+ * @ttsc/unplugin: bundler-agnostic ttsc plugin adapter.
  *
  * Re-exports the unified `unplugin` instance that carries named bundler
  * adapters (`.vite`, `.rollup`, `.rolldown`, `.webpack`, `.rspack`, `.esbuild`,

package/lib/turbopack.d.ts

@@ -36,7 +36,7 @@ export interface TtscTurbopackLoaderContext {
  *
  * Pass {@link TtscUnpluginOptions} through the rule's `options` object. The
  * loader returns the source unchanged for declaration files, `node_modules`
- * paths, and transforms that produce no change — mirroring the unplugin
+ * paths, and transforms that produce no change, mirroring the unplugin
  * adapters' `transformInclude` filter, since a broad rule glob routes
  * everything matching the extension through the loader.
  */

package/lib/turbopack.js

@@ -37,7 +37,7 @@ const transformCache = transform.createTtscTransformCache();
  *
  * Pass {@link TtscUnpluginOptions} through the rule's `options` object. The
  * loader returns the source unchanged for declaration files, `node_modules`
- * paths, and transforms that produce no change — mirroring the unplugin
+ * paths, and transforms that produce no change, mirroring the unplugin
  * adapters' `transformInclude` filter, since a broad rule glob routes
  * everything matching the extension through the loader.
  */

package/lib/turbopack.mjs

@@ -33,7 +33,7 @@ const transformCache = createTtscTransformCache();
  *
  * Pass {@link TtscUnpluginOptions} through the rule's `options` object. The
  * loader returns the source unchanged for declaration files, `node_modules`
- * paths, and transforms that produce no change — mirroring the unplugin
+ * paths, and transforms that produce no change, mirroring the unplugin
  * adapters' `transformInclude` filter, since a broad rule glob routes
  * everything matching the extension through the loader.
  */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ttsc/unplugin",
-  "version": "0.16.3",
+  "version": "0.16.4",
   "description": "Bundler adapters for ttsc plugins.",
   "main": "lib/index.js",
   "module": "lib/index.mjs",
@@ -102,7 +102,7 @@
     "tslib": "^2.8.1",
     "typescript": "7.0.1-rc",
     "vite": "^7.1.12",
-    "ttsc": "0.16.3"
+    "ttsc": "0.16.4"
   },
   "repository": {
     "type": "git",

package/src/core/index.ts

@@ -20,7 +20,7 @@ export const sourceFilePattern = /\.[cm]?tsx?$/;
 /** Matches any path segment that is a `node_modules` directory (cross-platform). */
 const nodeModulesPattern = /(?:^|[/\\])node_modules(?:[/\\]|$)/;
 /**
- * Matches virtual module ids — Rollup/Vite use a leading NUL byte (`\0`) as
+ * Matches virtual module ids: Rollup/Vite use a leading NUL byte (`\0`) as
  * convention.
  */
 const virtualModulePattern = /\0/;

package/src/core/options.ts

@@ -35,8 +35,8 @@ export interface TtscUnpluginOptions {
  * Fully-resolved plugin options with all defaults applied.
  *
  * Produced by {@link resolveOptions}; consumed internally by the transform
- * pipeline. Every field is present and normalised — callers should not
- * construct this type directly.
+ * pipeline. Every field is present and normalised; callers should not construct
+ * this type directly.
  */
 export interface ResolvedTtscUnpluginOptions {
   /** Compiler-options overlay applied on top of the discovered tsconfig. */

package/src/core/transform.ts

@@ -46,7 +46,7 @@ export interface TtscTransformAlias {
  * input file. On subsequent transforms the cached entry is validated by
  * re-hashing the project and comparing against {@link inputHashes}; a mismatch
  * triggers a full re-transform. Both sides hash the same set of files (the
- * project directory walk), so the comparison is meaningful — keying the
+ * project directory walk), so the comparison is meaningful; keying the
  * compiler's out-of-walk output paths on only one side is what made the cache
  * miss on every module.
  */
@@ -113,7 +113,7 @@ export interface TtscTransformHooks {
  * @param cache - Optional per-build cache; cleared by the caller on
  *   `buildStart`.
  * @param hooks - Optional adapter callbacks; see {@link TtscTransformHooks}.
- *   Dependency notifications fire on cache hits too — watch registrations are
+ *   Dependency notifications fire on cache hits too; watch registrations are
  *   per build, not per compilation.
  */
 export async function transformTtsc(
@@ -191,7 +191,7 @@ export async function transformTtsc(
  * The transform envelope's `dependencies` keys mirror the `typescript` keys
  * (project-relative); values may be project-relative or absolute. Every path is
  * absolutized against the project root and deduplicated, and the file itself is
- * dropped — the bundler already watches the module it transforms.
+ * dropped; the bundler already watches the module it transforms.
  */
 function notifyFileDependencies(
   hooks: TtscTransformHooks | undefined,
@@ -311,9 +311,9 @@ export function createTransformResult(
  *
  * Re-hashes every file under the project root and overlays the current module's
  * in-memory source, then compares the snapshot against the one captured when
- * the result was produced. Any input under the project root changing — the
- * module itself or a sibling the plugin reads — invalidates the entry and
- * forces a re-transform. Out-of-walk inputs a plugin pulls in (`node_modules`
+ * the result was produced. Any input under the project root changing (the
+ * module itself or a sibling the plugin reads) invalidates the entry and forces
+ * a re-transform. Out-of-walk inputs a plugin pulls in (`node_modules`
  * declarations, sibling-package sources) are not seen here; adapters invalidate
  * on those through the reported `dependencies` → `addWatchFile` → the bundler's
  * next `buildStart` cache clear.
@@ -323,8 +323,8 @@ export function createTransformResult(
  * the key universe. The earlier implementation overlaid the compiler's output
  * keys here on only one side; those keys include out-of-walk program inputs
  * (`node_modules` declarations, sibling-package sources), so the snapshots
- * never matched and the cache missed on every module — re-transforming the
- * whole project once per file on any project that imports a typed dependency.
+ * never matched and the cache missed on every module; re-transforming the whole
+ * project once per file on any project that imports a typed dependency.
  */
 function matchesCachedSource(
   cached: TtscCachedProjectTransform,
@@ -340,8 +340,8 @@ function matchesCachedSource(
 /**
  * Build the input-hash snapshot stored alongside a fresh compiler result.
  *
- * Hashes every file under the project directory — the exact universe
- * {@link matchesCachedSource} re-hashes to validate — then overlays the
+ * Hashes every file under the project directory (the exact universe
+ * {@link matchesCachedSource} re-hashes to validate), then overlays the
  * in-memory source for the module that triggered the compile so unsaved editor
  * content is captured correctly.
  *
@@ -593,7 +593,7 @@ function normalizePluginConfigForGeneratedTsconfig(
  * project's own `paths` wholesale. The overlay therefore re-states the
  * project's effective mappings first, so tsconfig-only aliases keep resolving;
  * inline `compilerOptions.paths` from the plugin options ride on top, and the
- * bundler aliases win last — they mirror what the bundler will actually do at
+ * bundler aliases win last; they mirror what the bundler will actually do at
  * resolve time.
  *
  * No `baseUrl` is emitted: TypeScript-Go removed the option (TS5102), and all
@@ -838,7 +838,7 @@ function formatUnknownError(error: unknown): string {
  * If `tsconfig` is supplied it is returned as-is (absolute) or resolved from
  * `process.cwd()` (relative). Otherwise the function walks ancestor directories
  * starting at `file`'s directory, returning the first `tsconfig.json` found.
- * Falls back to `<cwd>/tsconfig.json` when no ancestor contains one — the
+ * Falls back to `<cwd>/tsconfig.json` when no ancestor contains one; the
  * compiler will error if that file does not exist, which is the correct
  * behavior for a mis-configured project.
  */
@@ -856,7 +856,7 @@ function resolveTsconfig(file: string, tsconfig?: string): string {
       return candidate;
     }
     const parent = path.dirname(current);
-    // Reached filesystem root — stop walking.
+    // Reached filesystem root, stop walking.
     if (parent === current) {
       break;
     }

package/src/core/tsconfigPaths.ts

@@ -10,8 +10,8 @@ import path from "node:path";
  * is the whole object from the nearest config in the chain that declares one
  * (own config first, then `extends` entries in reverse priority order).
  * Relative targets are anchored at the directory of the config that declares
- * them — TypeScript-Go resolves inherited relative `paths` against the
- * declaring file, not the extending one.
+ * them. TypeScript-Go resolves inherited relative `paths` against the declaring
+ * file, not the extending one.
  *
  * The generated transform tsconfig replaces `paths` wholesale (standard
  * `extends` semantics), so the alias overlay must re-state these base mappings
@@ -71,7 +71,7 @@ interface IDeclaredPaths {
 /**
  * Locate the nearest `compilerOptions.paths` declaration in the `extends` chain
  * rooted at `tsconfig`. The own config wins over its bases; within an `extends`
- * array, later entries win over earlier ones. `seen` breaks circular chains —
+ * array, later entries win over earlier ones. `seen` breaks circular chains;
  * the compiler reports the actual config error.
  */
 function findDeclaredPaths(
@@ -132,7 +132,7 @@ function extendsSpecifiers(extended: unknown): string[] {
  * Resolve an `extends` specifier to an absolute config path using TypeScript's
  * rules: absolute paths and relative specifiers get `.json` /
  * `tsconfig.json`-directory fallbacks; bare specifiers go through Node's module
- * resolver scoped to the declaring config. Returns `null` instead of throwing —
+ * resolver scoped to the declaring config. Returns `null` instead of throwing;
  * the compiler reports unresolvable `extends` itself.
  */
 function resolveExtendsConfig(
@@ -205,7 +205,7 @@ function resolveRealPath(location: string): string {
 
 /**
  * Parse a JSONC (JSON with Comments) string by stripping comments and trailing
- * commas before handing off to `JSON.parse`. A leading UTF-8 BOM is dropped —
+ * commas before handing off to `JSON.parse`. A leading UTF-8 BOM is dropped;
  * `JSON.parse` rejects it, and this reader must not lose `paths` for a config
  * the compiler accepts.
  */

package/src/index.ts

@@ -1,5 +1,5 @@
 /**
- * @ttsc/unplugin — bundler-agnostic ttsc plugin adapter.
+ * @ttsc/unplugin: bundler-agnostic ttsc plugin adapter.
  *
  * Re-exports the unified `unplugin` instance that carries named bundler
  * adapters (`.vite`, `.rollup`, `.rolldown`, `.webpack`, `.rspack`, `.esbuild`,

package/src/turbopack.ts

@@ -57,7 +57,7 @@ const transformCache = createTtscTransformCache();
  *
  * Pass {@link TtscUnpluginOptions} through the rule's `options` object. The
  * loader returns the source unchanged for declaration files, `node_modules`
- * paths, and transforms that produce no change — mirroring the unplugin
+ * paths, and transforms that produce no change, mirroring the unplugin
  * adapters' `transformInclude` filter, since a broad rule glob routes
  * everything matching the extension through the loader.
  */