@vzn/vx-migrate 0.0.634 → 0.0.636

package/README.md

@@ -1,6 +1,8 @@
 # @vzn/vx-migrate
 
-Everything for adopting [`@vzn/vx`](https://github.com/vznjs/vx) from Turborepo, Nx or Vite Task, in one package with zero dependencies:
+Website: <https://vznjs.github.io/vx/> · this plugin: <https://vznjs.github.io/vx/plugins/vx-migrate/> · source: <https://github.com/vznjs/vx>
+
+Everything for adopting [`@vzn/vx`](https://vznjs.github.io/vx/) from Turborepo, Nx or Vite Task, in one package with zero dependencies:
 
 - **`turbo()`** — a temporary start for a Turbo repository: the plugin fills vx's `project` stage from `turbo.json` and each package's `package.json` scripts until the migrator writes native config.
 - **`nx()`** — the same temporary start for an Nx repository, filled from Nx's resolved project graph. Executor targets (`@nx/js:tsc`, `@nx/vite:build`, your own) run as themselves through **`nx-exec`**, one executor per process.
@@ -232,7 +234,7 @@ Your `package.json` scripts are never edited. `--dry` installs nothing and says
 
 ### Turbo
 
-Reads the root pipeline (`tasks` in Turbo 2, `pipeline` in Turbo 1), per-package `turbo.json` `extends` overlays and each package's scripts, through the same mapper `turbo()` runs live — so the written configs say what the plugin was doing. Turbo's global fields become a generated root `vx-preset.ts` each config imports and spreads: TypeScript composition replaces global config. A package whose `tsconfig.json` is a composite project (or sets `rootDir`) and takes in its config declares the values it uses instead: `tsc` refuses a file outside the package (TS6059, TS6307; withastro/astro's `scripts/`). So does a task's `env` that several configs share (`buildEnv`), where inline it would repeat in every package (vercel/ai: 63 names, twice in each of ~100 configs, half the output). Turbo's `//#` root tasks are written to a `vx.config.ts` at the workspace root, which makes the root a project (core's D-39), and a package task's `//#x` edge reaches it. When a `vx.workspace.ts` already exists without one, the report names the `@vzn/vx-lockfile` plugin for the repo's lockfile: Turbo keys each package on its own lockfile entries, and core keys every task on the whole file until a plugin claims it.
+Reads the root pipeline (`tasks` in Turbo 2, `pipeline` in Turbo 1), per-package `turbo.json` `extends` overlays and each package's scripts, through the same mapper `turbo()` runs live — so the written configs say what the plugin was doing. Turbo's global fields become a generated root `vx-preset.ts` each config imports and spreads: TypeScript composition replaces global config. A config that a `tsconfig*.json` in its directory or above (below the root) takes in, where that project is composite or sets `rootDir`, declares the values it uses instead: `tsc` refuses a file outside the package (TS6059, TS6307; withastro/astro's `scripts/` and the `performance/` project its `packages/astro/tsconfig.test.json` takes in). So does a task's `env` that several configs share (`buildEnv`), where inline it would repeat in every package (vercel/ai: 63 names, twice in each of ~100 configs, half the output). Turbo's `//#` root tasks are written to a `vx.config.ts` at the workspace root, which makes the root a project (core's D-39), and a package task's `//#x` edge reaches it. When a `vx.workspace.ts` already exists without one, the report names the `@vzn/vx-lockfile` plugin for the repo's lockfile: Turbo keys each package on its own lockfile entries, and core keys every task on the whole file until a plugin claims it.
 
 | Turborepo                           | vx                                                                                                |
 | ----------------------------------- | ------------------------------------------------------------------------------------------------- |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vzn/vx-migrate",
-  "version": "0.0.634",
+  "version": "0.0.636",
   "license": "MIT",
   "description": "Adopt @vzn/vx from Turborepo or Nx: run the repo unchanged, migrate it to vx.config.ts, and keep your Turbo or Nx remote cache",
   "keywords": [
@@ -8,6 +8,7 @@
     "vx-plugin",
     "monorepo",
     "turborepo",
+    "turbo",
     "nx",
     "migration",
     "remote-cache"
@@ -39,7 +40,7 @@
     "access": "public"
   },
   "peerDependencies": {
-    "@vzn/vx": "^0.0.634"
+    "@vzn/vx": "^0.0.636"
   },
   "repository": {
     "type": "git",

package/src/migrate-turbo.ts

@@ -80,7 +80,9 @@ export async function migrateTurbo(
     ])
     for (const t of p.tasks) for (const kind of t.uses) used.add(PRESET_NAMES[kind])
     const readsManifest = p.tasks.some((t) => JSON.stringify(t.task ?? {}).includes('"pkg.'))
-    const sealed = used.size > 0 && sealsConfig(path.resolve(root, p.dir), `vx.config.${format}`)
+    const sealed =
+      used.size > 0 &&
+      sealsConfig(root, path.join(path.resolve(root, p.dir), `vx.config.${format}`))
     if (used.size > 0 && !sealed) imported = true
     if (sealed) anySealed = true
     return {

package/src/sealed-tsconfig.ts

@@ -1,15 +1,18 @@
-// A package whose tsconfig is a composite project (or sets `rootDir`)
-// refuses a source file outside its directory: withastro/astro's
+// A tsconfig that is a composite project (or sets `rootDir`) refuses a
+// source file outside its directory: withastro/astro's
 // `scripts/tsconfig.json` type-checked the written `vx.config.mjs`, and its
-// import of the root `vx-preset.mjs` failed the build (TS6059, TS6307). Such
-// a package's config declares the preset values it uses itself.
+// import of the root `vx-preset.mjs` failed the build (TS6059, TS6307). So
+// did `packages/astro/tsconfig.test.json`, which takes in the nested
+// `performance/vx.config.mjs`. A config such a project takes in declares
+// the preset values it uses itself.
 
-import { readFileSync } from 'node:fs'
+import { readdirSync, readFileSync } from 'node:fs'
 import path from 'node:path'
 
 type TsConfig = {
   extends?: unknown
   include?: unknown
+  exclude?: unknown
   files?: unknown
   compilerOptions?: { composite?: unknown; rootDir?: unknown }
 }
@@ -22,33 +25,65 @@ function read(file: string): TsConfig | null {
   }
 }
 
-/** Does `dir/tsconfig.json` take `dir/<config>` into a project that refuses files outside `dir`? */
-export function sealsConfig(dir: string, config: string): boolean {
-  const own = read(path.join(dir, 'tsconfig.json'))
-  if (own === null) return false
-  // `include` and `files` are not inherited past the file that sets them
-  // relative to it; the compiler options are, through `extends`.
-  let sealed = false
-  let at: TsConfig | null = own
-  let from = dir
+/** A tsconfig glob as `Bun.Glob` reads it, relative to the tsconfig's own directory. */
+function pattern(p: string): string {
+  const rel = p.replace(/^\$\{configDir\}\/?/, '').replace(/^\.\//, '')
+  if (rel === '' || rel === '.') return '**/*'
+  // A directory names everything under it, as tsc reads it.
+  return /[*?{]/.test(rel) || /\.[A-Za-z0-9]+$/.test(rel) ? rel : `${rel.replace(/\/$/, '')}/**/*`
+}
+
+/** Does the project `file` states take in `rel` (relative to its directory) and refuse files outside it? */
+function seals(file: string, rel: string): boolean {
+  let sealed: boolean | undefined
+  let include: unknown
+  let exclude: unknown
+  let files: unknown
+  let at: TsConfig | null = read(file)
+  let from = path.dirname(file)
+  // The nearest file that states a field decides it, as `extends` resolves.
   for (let depth = 0; at !== null && depth < 8; depth++) {
     const o = at.compilerOptions
-    if (o?.composite === true || typeof o?.rootDir === 'string') {
-      sealed = true
-      break
-    }
+    if (sealed === undefined && o?.composite !== undefined) sealed = o.composite === true
+    if (sealed !== true && typeof o?.rootDir === 'string') sealed = true
+    include ??= at.include
+    exclude ??= at.exclude
+    files ??= at.files
     const ext = at.extends
-    // A package name (`@tsconfig/node20`) seals nothing a repo would ship.
+    // A package (`@tsconfig/node20`) is not followed: what it seals is rare.
     if (typeof ext !== 'string' || !ext.startsWith('.')) break
-    const file = path.resolve(from, ext.endsWith('.json') ? ext : `${ext}.json`)
-    from = path.dirname(file)
-    at = read(file)
+    const next = path.resolve(from, ext.endsWith('.json') ? ext : `${ext}.json`)
+    from = path.dirname(next)
+    at = read(next)
+  }
+  if (sealed !== true) return false
+  const hit = (list: unknown): boolean =>
+    Array.isArray(list) &&
+    list.some((g) => typeof g === 'string' && new Bun.Glob(pattern(g)).match(rel))
+  if (hit(exclude)) return false
+  if (Array.isArray(files) && files.some((f) => typeof f === 'string' && pattern(f) === rel))
+    return true
+  if (Array.isArray(include)) return hit(include)
+  // `files` alone lists exactly what it compiles; neither means everything.
+  return !Array.isArray(files)
+}
+
+/**
+ * Is `config` (absolute) taken in by a sealing tsconfig (`tsconfig*.json`)
+ * in its directory or one above it, below `root`? The root's own project
+ * holds the preset, so it refuses nothing.
+ */
+export function sealsConfig(root: string, config: string): boolean {
+  for (let dir = path.dirname(config); dir !== root && dir.startsWith(root);) {
+    let names: string[] = []
+    try {
+      names = readdirSync(dir).filter((n) => /^tsconfig.*\.json$/.test(n))
+    } catch {}
+    const rel = path.relative(dir, config).split(path.sep).join('/')
+    if (names.some((n) => seals(path.join(dir, n), rel))) return true
+    const up = path.dirname(dir)
+    if (up === dir) break
+    dir = up
   }
-  if (!sealed) return false
-  if (Array.isArray(own.include))
-    return own.include.some(
-      (g) => typeof g === 'string' && new Bun.Glob(g.replace(/^\.\//, '')).match(config),
-    )
-  // `files` alone lists exactly what it compiles.
-  return !Array.isArray(own.files)
+  return false
 }