@gjsify/rolldown-plugin-gjsify 0.26.1 → 0.27.1

package/lib/globals.d.ts

@@ -1,4 +1,4 @@
-export { resolveGlobalsList, writeRegisterInjectFile, isRegisterPathResolvable, filterResolvableRegisterPaths } from './utils/scan-globals.js';
+export { resolveGlobalsList, writeRegisterInjectFile, isRegisterPathResolvable, filterResolvableRegisterPaths, } from './utils/scan-globals.js';
 export { detectFreeGlobals, detectGjsAmbientGlobals, detectNodeGiModuleImports, GJS_AMBIENT_GLOBALS, } from './utils/detect-free-globals.js';
 export { detectAutoGlobals, detectNodeGiGlobals, describeGiBackedInjection } from './utils/auto-globals.js';
 export type { AutoGlobalsResult, DetectAutoGlobalsOptions, AnalysisOptions } from './utils/auto-globals.js';

package/lib/globals.js

@@ -4,6 +4,6 @@
 // (or auto-detect via the iterative multi-pass build) and write the inject
 // stub that the plugin picks up via its `autoGlobalsInject` option. See the
 // "Tree-shakeable Globals" section in AGENTS.md for the architecture.
-export { resolveGlobalsList, writeRegisterInjectFile, isRegisterPathResolvable, filterResolvableRegisterPaths } from './utils/scan-globals.js';
+export { resolveGlobalsList, writeRegisterInjectFile, isRegisterPathResolvable, filterResolvableRegisterPaths, } from './utils/scan-globals.js';
 export { detectFreeGlobals, detectGjsAmbientGlobals, detectNodeGiModuleImports, GJS_AMBIENT_GLOBALS, } from './utils/detect-free-globals.js';
 export { detectAutoGlobals, detectNodeGiGlobals, describeGiBackedInjection } from './utils/auto-globals.js';

package/lib/index.d.ts

@@ -2,7 +2,7 @@ export * from './types/index.js';
 export * from './utils/index.js';
 export * from './app/index.js';
 export * from './library/index.js';
-export { REWRITE_FILTER, getBundleDirFromOutput, rewriteContents, shouldRewrite, nodeModulesPathRewritePlugin, } from './plugins/rewrite-node-modules-paths.js';
+export { REWRITE_FILTER, extractPackageSpec, getBundleDirFromOutput, rewriteContents, shouldRewrite, nodeModulesPathRewritePlugin, } from './plugins/rewrite-node-modules-paths.js';
 export type { NodeModulesPathRewriteOptions, RewriteResult } from './plugins/rewrite-node-modules-paths.js';
 export { processStubPlugin, GJS_PROCESS_STUB, composeBanner } from './plugins/process-stub.js';
 export type { ProcessStubPluginOptions } from './plugins/process-stub.js';
@@ -18,7 +18,7 @@ export { externalsPlugin } from './plugins/externals.js';
 export type { ExternalsPredicate, ExternalsPluginOptions } from './plugins/externals.js';
 export { unresolvedWorkspaceImportPlugin, classifyImport, isWorkspaceSpecifier, formatUnresolvedWorkspaceImport, buildReverseAliasIndex, UnresolvedWorkspaceImportError, } from './plugins/unresolved-workspace-import.js';
 export type { WorkspaceImportGuardOptions, WorkspaceImportGuardTarget, ImportVerdict, ClassifyImportInput, UnresolvedWorkspaceImportDetails, } from './plugins/unresolved-workspace-import.js';
-export { napiNodeAddonPlugin, resolveAddonPath, nearestPackageRoot, classifySpecifier, directNodeShim, nodeGypBuildShim, bindingsShim, napiRsShim, ADDON_FILTER_RE, isNapiRsPackageJson, isNapiRsSibling, detectNapiRsEntry, AddonNotBuiltError, } from './plugins/napi-node-addon.js';
+export { napiNodeAddonPlugin, resolveAddonPath, nearestPackageRoot, classifySpecifier, directNodeShim, nodeGypBuildShim, bindingsShim, napiRsShim, ADDON_FILTER_RE, isNapiRsPackageJson, isNapiRsSibling, isGjsifyNativeBridge, detectNapiRsEntry, hostNapiRsTriple, AddonNotBuiltError, } from './plugins/napi-node-addon.js';
 export type { NapiNodeAddonPluginOptions, AddonPackageJson } from './plugins/napi-node-addon.js';
 export { platformResolvePlugin, detectNativescriptPlatform, nativescriptPlatformDefines, } from './plugins/platform-resolve.js';
 export type { PlatformResolvePluginOptions, NativescriptPlatform } from './plugins/platform-resolve.js';

package/lib/index.js

@@ -3,7 +3,7 @@ export * from './types/index.js';
 export * from './utils/index.js';
 export * from './app/index.js';
 export * from './library/index.js';
-export { REWRITE_FILTER, getBundleDirFromOutput, rewriteContents, shouldRewrite, nodeModulesPathRewritePlugin, } from './plugins/rewrite-node-modules-paths.js';
+export { REWRITE_FILTER, extractPackageSpec, getBundleDirFromOutput, rewriteContents, shouldRewrite, nodeModulesPathRewritePlugin, } from './plugins/rewrite-node-modules-paths.js';
 export { processStubPlugin, GJS_PROCESS_STUB, composeBanner } from './plugins/process-stub.js';
 export { cssAsStringPlugin } from './plugins/css-as-string.js';
 export { textLoaderPlugin } from './plugins/text-loader.js';
@@ -12,7 +12,7 @@ export { aliasPlugin } from './plugins/alias.js';
 export { gjsImportsEmptyPlugin } from './plugins/gjs-imports-empty.js';
 export { externalsPlugin } from './plugins/externals.js';
 export { unresolvedWorkspaceImportPlugin, classifyImport, isWorkspaceSpecifier, formatUnresolvedWorkspaceImport, buildReverseAliasIndex, UnresolvedWorkspaceImportError, } from './plugins/unresolved-workspace-import.js';
-export { napiNodeAddonPlugin, resolveAddonPath, nearestPackageRoot, classifySpecifier, directNodeShim, nodeGypBuildShim, bindingsShim, napiRsShim, ADDON_FILTER_RE, isNapiRsPackageJson, isNapiRsSibling, detectNapiRsEntry, AddonNotBuiltError, } from './plugins/napi-node-addon.js';
+export { napiNodeAddonPlugin, resolveAddonPath, nearestPackageRoot, classifySpecifier, directNodeShim, nodeGypBuildShim, bindingsShim, napiRsShim, ADDON_FILTER_RE, isNapiRsPackageJson, isNapiRsSibling, isGjsifyNativeBridge, detectNapiRsEntry, hostNapiRsTriple, AddonNotBuiltError, } from './plugins/napi-node-addon.js';
 export { platformResolvePlugin, detectNativescriptPlatform, nativescriptPlatformDefines, } from './plugins/platform-resolve.js';
 export * from './plugin.js';
 import { gjsifyPlugin } from './plugin.js';

package/lib/plugins/napi-node-addon.d.ts

@@ -67,8 +67,39 @@ export interface AddonPackageJson {
     exports?: unknown;
     browser?: string;
     napi?: unknown;
+    gjsify?: unknown;
     optionalDependencies?: Record<string, string>;
 }
+/**
+ * Is this manifest a gjsify NATIVE BRIDGE whose prebuilds live in per-target
+ * sibling packages (ADR 0017) — `@gjsify/webgl` + `@gjsify/webgl-darwin-x64`, …?
+ *
+ * Such a bridge ships a GObject-Introspection typelib plus a `.so`/`.dylib`/`.dll`
+ * loaded through `gi://`, NEVER a Node-API `.node` addon, so it must never be
+ * routed through `loadAddon()`.
+ *
+ * It has to be excluded EXPLICITLY because the two conventions are
+ * indistinguishable by name: ADR 0017 spells a target `<os>-<arch>` and names the
+ * package `<self>-<os>-<arch>` in `optionalDependencies` — which is exactly
+ * napi-rs' `<self>-<triple>` sibling scheme whenever the target happens to be a
+ * name napi-rs also uses. On Linux the two vocabularies differ by the libc token
+ * (`linux-x64` vs napi-rs' `linux-x64-gnu`), so `hostNapiRsTriple()` never matched
+ * and nothing fired; on macOS napi-rs' triple IS `darwin-x64` / `darwin-arm64`,
+ * so every split bridge looked like a napi-rs package to
+ * {@link isNapiRsPackageJson} and {@link resolveNapiRsEntryAddon} then probed
+ * `ctx.resolve('@gjsify/webgl-darwin-x64')` — an artifact-only package with no JS
+ * entry at all. That probe does not return null: the `unresolved-workspace-import`
+ * guard (correctly) treats an unresolvable bare `@gjsify/*` as FATAL, so
+ * `gjsify build --app gjs` of any consumer of any split bridge died on darwin with
+ * "cannot resolve the workspace package" — invisible to every Linux CI job.
+ *
+ * `gjsify.platforms` is the right discriminator: it is the OS-axis declaration
+ * every native bridge carries (§ Runtime & platform model) and no napi-rs package
+ * has any reason to declare it.
+ *
+ * Exported for the unit tests.
+ */
+export declare function isGjsifyNativeBridge(pkg: AddonPackageJson): boolean;
 /**
  * A package.json describes a napi-rs generated-loader package when EITHER
  * signal holds — both are package.json-level (not source sniffing):
@@ -108,6 +139,16 @@ export declare function detectNapiRsEntry(entryFile: string): {
  * package's binaries. Exported for the unit tests.
  */
 export declare function isNapiRsSibling(pkg: AddonPackageJson, dep: string): boolean;
+/**
+ * The napi-rs short platform triple for the CURRENT host (`linux-x64-gnu`,
+ * `darwin-arm64`, `win32-x64-msvc`, …) — the tail napi-rs stamps into a sibling
+ * package name (`@node-rs/argon2-linux-x64-gnu`) and a local binary
+ * (`argon2.linux-x64-gnu.node`). Selects BOTH the sibling package and the
+ * local-file fallback — see `resolveNapiRsEntryAddon` for why the sibling path
+ * cannot just take whatever resolves. Returns null for a host napi-rs doesn't
+ * name, and the caller then widens rather than guessing.
+ */
+export declare function hostNapiRsTriple(): string | null;
 /**
  * Transparent `.node`-addon loader for `gjsify build --app gjs`.
  *

package/lib/plugins/napi-node-addon.js

@@ -384,6 +384,42 @@ export function classifySpecifier(source) {
         return { kind: 'napi-rs-candidate' };
     return null;
 }
+/**
+ * Is this manifest a gjsify NATIVE BRIDGE whose prebuilds live in per-target
+ * sibling packages (ADR 0017) — `@gjsify/webgl` + `@gjsify/webgl-darwin-x64`, …?
+ *
+ * Such a bridge ships a GObject-Introspection typelib plus a `.so`/`.dylib`/`.dll`
+ * loaded through `gi://`, NEVER a Node-API `.node` addon, so it must never be
+ * routed through `loadAddon()`.
+ *
+ * It has to be excluded EXPLICITLY because the two conventions are
+ * indistinguishable by name: ADR 0017 spells a target `<os>-<arch>` and names the
+ * package `<self>-<os>-<arch>` in `optionalDependencies` — which is exactly
+ * napi-rs' `<self>-<triple>` sibling scheme whenever the target happens to be a
+ * name napi-rs also uses. On Linux the two vocabularies differ by the libc token
+ * (`linux-x64` vs napi-rs' `linux-x64-gnu`), so `hostNapiRsTriple()` never matched
+ * and nothing fired; on macOS napi-rs' triple IS `darwin-x64` / `darwin-arm64`,
+ * so every split bridge looked like a napi-rs package to
+ * {@link isNapiRsPackageJson} and {@link resolveNapiRsEntryAddon} then probed
+ * `ctx.resolve('@gjsify/webgl-darwin-x64')` — an artifact-only package with no JS
+ * entry at all. That probe does not return null: the `unresolved-workspace-import`
+ * guard (correctly) treats an unresolvable bare `@gjsify/*` as FATAL, so
+ * `gjsify build --app gjs` of any consumer of any split bridge died on darwin with
+ * "cannot resolve the workspace package" — invisible to every Linux CI job.
+ *
+ * `gjsify.platforms` is the right discriminator: it is the OS-axis declaration
+ * every native bridge carries (§ Runtime & platform model) and no napi-rs package
+ * has any reason to declare it.
+ *
+ * Exported for the unit tests.
+ */
+export function isGjsifyNativeBridge(pkg) {
+    const gjsify = pkg?.gjsify;
+    if (gjsify === null || typeof gjsify !== 'object')
+        return false;
+    const { platforms, prebuilds } = gjsify;
+    return Array.isArray(platforms) || typeof prebuilds === 'string';
+}
 /**
  * A package.json describes a napi-rs generated-loader package when EITHER
  * signal holds — both are package.json-level (not source sniffing):
@@ -576,6 +612,10 @@ function napiSiblingPrefixes(pkg) {
 export function isNapiRsSibling(pkg, dep) {
     if (!NAPI_RS_TRIPLE_RE.test(dep))
         return false;
+    // A gjsify ADR-0017 platform package wears the same name — see
+    // {@link isGjsifyNativeBridge} for the darwin-only build break that caused.
+    if (isGjsifyNativeBridge(pkg))
+        return false;
     return napiSiblingPrefixes(pkg).some((prefix) => dep.startsWith(`${prefix}-`));
 }
 /**
@@ -587,7 +627,7 @@ export function isNapiRsSibling(pkg, dep) {
  * cannot just take whatever resolves. Returns null for a host napi-rs doesn't
  * name, and the caller then widens rather than guessing.
  */
-function hostNapiRsTriple() {
+export function hostNapiRsTriple() {
     const platform = process.platform;
     const arch = process.arch;
     const archTok = {
@@ -650,7 +690,22 @@ async function resolveNapiRsEntryAddon(ctx, pkgRoot, pkg, importer) {
     // loaders do, so this matches the binary Node would have loaded.
     const ordered = triple === null ? siblings : siblings.filter((dep) => dep.endsWith(`-${triple}`));
     for (const dep of ordered) {
-        const resolved = await ctx.resolve(dep, importer, { skipSelf: true });
+        // This resolve is a QUESTION ("is a host-triple binary installed?"), but it
+        // can THROW rather than answer: `skipSelf` skips only THIS plugin, so the
+        // `unresolved-workspace-import` guard still runs at `order:'post'` and
+        // (correctly, for a real import) makes an unresolvable bare `@gjsify/*`
+        // FATAL. A misread sibling name then kills the whole build instead of
+        // declining — measured on darwin, where every ADR-0017 platform package
+        // matched this path. The name check above is the fix; this keeps the class
+        // from ever being fatal again, and says which specifier was asked about.
+        let resolved = null;
+        try {
+            resolved = await ctx.resolve(dep, importer, { skipSelf: true });
+        }
+        catch (err) {
+            warnSafe(ctx, `[gjsify-napi] probing the platform sibling "${dep}" of "${pkg.name ?? pkgRoot}" failed; not rewriting its entry (${err instanceof Error ? err.message.split('\n')[0] : String(err)})`);
+            continue;
+        }
         if (!resolved)
             continue;
         const abs = rawAddonPath(resolved.id);

package/lib/plugins/rewrite-node-modules-paths.d.ts

@@ -19,8 +19,30 @@ export declare function getBundleDirFromOutput(opts: {
  *   ".../node_modules/typedoc/dist/lib/app.js"   → "typedoc/dist/lib/app.js"
  *   ".../node_modules/@scope/name/sub.js"        → "@scope/name/sub.js"
  *   ".../node_modules/a/node_modules/b/file.js"  → "b/file.js"
+ *
+ * The result is a module SPECIFIER, not a path, so it is always `/`-separated.
+ *
+ * On win32 the incoming path is `C:\…\node_modules\typescript\lib\_tsc.js` and
+ * the `node_modules/` marker never matched, so this returned the ABSOLUTE
+ * BUILD-MACHINE PATH unchanged — and `shouldRewrite` above tests
+ * `includes('node_modules')` without a separator, so the rewriter still fired
+ * and baked that path into the bundle as the runtime resolve spec. Measured on
+ * win32 x64 building `@gjsify/tsc`:
+ *
+ *   linux:  To(`typescript/lib/_tsc.js`)                        → retargets
+ *   win32:  To(`C:\\src\\werkstatt\\gjsify\\gjsify\\node_mod…`) → unshippable
+ *
+ * `@gjsify/tsc`'s `scripts/build-bundle.mjs` caught it ("expected runtime
+ * path-rewrite spec … not found in bundle — has the node-modules path rewriter
+ * changed?") and refused to ship, which is why this surfaced as a build failure
+ * rather than as a bundle that resolves nothing on someone else's machine.
+ *
+ * The conversion is win32-ONLY: on POSIX a backslash is a legitimate FILENAME
+ * character, so rewriting it there would corrupt a real path. `platform` is
+ * injected so both branches are unit-testable from either host — the same shape
+ * `utils/entry-points.ts` and `cli/src/utils/win32-command.ts` use.
  */
-export declare function extractPackageSpec(path: string): string;
+export declare function extractPackageSpec(path: string, platform?: string): string;
 export interface RewriteResult {
     code: string;
     moduleType?: 'ts' | 'js';

package/lib/plugins/rewrite-node-modules-paths.js

@@ -104,11 +104,34 @@ function moduleTypeForPath(path) {
  *   ".../node_modules/typedoc/dist/lib/app.js"   → "typedoc/dist/lib/app.js"
  *   ".../node_modules/@scope/name/sub.js"        → "@scope/name/sub.js"
  *   ".../node_modules/a/node_modules/b/file.js"  → "b/file.js"
+ *
+ * The result is a module SPECIFIER, not a path, so it is always `/`-separated.
+ *
+ * On win32 the incoming path is `C:\…\node_modules\typescript\lib\_tsc.js` and
+ * the `node_modules/` marker never matched, so this returned the ABSOLUTE
+ * BUILD-MACHINE PATH unchanged — and `shouldRewrite` above tests
+ * `includes('node_modules')` without a separator, so the rewriter still fired
+ * and baked that path into the bundle as the runtime resolve spec. Measured on
+ * win32 x64 building `@gjsify/tsc`:
+ *
+ *   linux:  To(`typescript/lib/_tsc.js`)                        → retargets
+ *   win32:  To(`C:\\src\\werkstatt\\gjsify\\gjsify\\node_mod…`) → unshippable
+ *
+ * `@gjsify/tsc`'s `scripts/build-bundle.mjs` caught it ("expected runtime
+ * path-rewrite spec … not found in bundle — has the node-modules path rewriter
+ * changed?") and refused to ship, which is why this surfaced as a build failure
+ * rather than as a bundle that resolves nothing on someone else's machine.
+ *
+ * The conversion is win32-ONLY: on POSIX a backslash is a legitimate FILENAME
+ * character, so rewriting it there would corrupt a real path. `platform` is
+ * injected so both branches are unit-testable from either host — the same shape
+ * `utils/entry-points.ts` and `cli/src/utils/win32-command.ts` use.
  */
-export function extractPackageSpec(path) {
+export function extractPackageSpec(path, platform = process.platform) {
+    const normalized = platform === 'win32' ? path.replaceAll('\\', '/') : path;
     const marker = 'node_modules/';
-    const idx = path.lastIndexOf(marker);
-    return idx < 0 ? path : path.slice(idx + marker.length);
+    const idx = normalized.lastIndexOf(marker);
+    return idx < 0 ? normalized : normalized.slice(idx + marker.length);
 }
 /**
  * The bare package name of a node_modules file spec (scoped names kept whole):

package/lib/utils/auto-globals.js

@@ -231,9 +231,7 @@ export async function detectAutoGlobals(analysisOptions, pluginOptions, gjsifyPl
     let detected = new Set();
     let currentInject = undefined;
     if (extraRegisterPaths.size > 0) {
-        const resolvableExtra = cwd
-            ? filterResolvableRegisterPaths(extraRegisterPaths, cwd)
-            : extraRegisterPaths;
+        const resolvableExtra = cwd ? filterResolvableRegisterPaths(extraRegisterPaths, cwd) : extraRegisterPaths;
         currentInject = (await writeRegisterInjectFile(resolvableExtra, cwd)) ?? undefined;
     }
     // Caller-provided plugins (e.g. PnP relay) survive every pass; the
@@ -317,7 +315,13 @@ export async function detectAutoGlobals(analysisOptions, pluginOptions, gjsifyPl
             catch (e) {
                 if (globalThis.process?.env
                     ?.GJSIFY_DEBUG_AUTO_GLOBALS) {
-                    const path = `/tmp/gjsify-auto-globals-failed-chunk-${i}.mjs`;
+                    // `tmpdir()`, not a literal `/tmp` — on Windows that wrote
+                    // to `<drive>:\tmp\`, and the `writeFileSync` is inside a
+                    // `catch`, so the dump silently did not appear where the
+                    // log line below says it did.
+                    const os = await import('node:os');
+                    const nodePath = await import('node:path');
+                    const path = nodePath.join(os.tmpdir(), `gjsify-auto-globals-failed-chunk-${i}.mjs`);
                     try {
                         // Dynamic `import()` on purpose: this is a debug-only
                         // branch and the module graph should not carry
@@ -368,9 +372,7 @@ export async function detectAutoGlobals(analysisOptions, pluginOptions, gjsifyPl
         // Union with the previously-injected set keeps growth monotonic
         // (an over-approximated superset must never shrink, or the subset
         // convergence check could oscillate).
-        const expanded = options.disableClosureExpansion
-            ? newDetected
-            : expandWithClosure(newDetected, excludeSet);
+        const expanded = options.disableClosureExpansion ? newDetected : expandWithClosure(newDetected, excludeSet);
         if (verbose && expanded.size > newDetected.size) {
             console.debug(`[gjsify] --globals auto: closure map expanded ${newDetected.size} → ${expanded.size} global(s)`);
         }

package/lib/utils/entry-points.d.ts

@@ -1,2 +1,2 @@
 export type EntryPoints = string | string[] | Record<string, string>;
-export declare const globToEntryPoints: (_entryPoints: EntryPoints | undefined, ignore?: string[]) => Promise<EntryPoints | undefined>;
+export declare const globToEntryPoints: (_entryPoints: EntryPoints | undefined, ignore?: string[], platform?: string) => Promise<EntryPoints | undefined>;

package/lib/utils/entry-points.js

@@ -36,18 +36,74 @@
 // `packages/infra/cli/src/entry-points.spec.ts` and
 // `tests/e2e/deterministic-library-build/`.
 import fastGlob from 'fast-glob';
+/** Never expandable to an entry point — the type-only exclusion from the header. */
 const DEFAULT_IGNORE = ['**/*.d.ts'];
+/**
+ * BLAST-RADIUS cap, added to a pattern that does not itself name `node_modules`.
+ *
+ * `ignore` prunes fast-glob's DIRECTORY traversal, not merely its results, so it
+ * bounds the walk: on the mis-formed pattern in {@link toGlobSeparators} it turns
+ * heap death into 32 ms. That matters beyond the one bug — the walk it stops runs
+ * into the workspace's RELATIVE `node_modules/@gjsify/*` symlinks, which cycle
+ * back into `packages/`.
+ *
+ * Conditional, and NOT a blanket default, because a package may legitimately
+ * bundle an entry that lives in there: `@gjsify/tsc`'s whole build is
+ * `gjsify build node_modules/typescript/lib/_tsc.js --app gjs`, and an
+ * unconditional ignore emptied its input and broke `build:infra` (caught by the
+ * closure build, not by a unit test — which is why the rule is stated as
+ * narrowly as it can be). The rule in one sentence: a WILDCARD never descends
+ * into `node_modules`, while a path that names it explicitly is honoured.
+ */
+const NODE_MODULES_IGNORE = '**/node_modules/**';
+function ignoreFor(pattern, ignore) {
+    return pattern.includes('node_modules') ? [...ignore] : [...ignore, NODE_MODULES_IGNORE];
+}
+/**
+ * Make a pattern safe to hand to fast-glob on Windows.
+ *
+ * fast-glob patterns are POSIX-only: `\` is its ESCAPE character, never a path
+ * separator. Its own source says so where it declines to use `path.normalize`
+ * (`fast-glob/out/utils/path.js`):
+ *
+ * > Because of this, we cannot use the standard `path.normalize` method,
+ * > because on Windows platform it will use of backslashes.
+ *
+ * A backslashed pattern does NOT fail cleanly, which is what made this
+ * expensive. `src\**\*.{ts,js}` contains no `/`, so fast-glob's
+ * `generateTasks` finds no static prefix and walks from `.` instead of from
+ * `src` — and its walker follows symlinks with unbounded depth and no cycle
+ * detection. In a workspace whose `node_modules/@gjsify/*` are RELATIVE
+ * symlinks back into `packages/`, that walk never terminates: RSS climbs until
+ * the heap dies, nothing ever matches, and no output file is written. Measured
+ * on win32 (issue #914): `@gjsify/utils` at 845 MB / 413 s CPU after 5 min with
+ * zero outputs, `@gjsify/rolldown-native` `FATAL ERROR: Ineffective
+ * mark-compacts near heap limit` after 33 min — reproduced verbatim on Linux by
+ * feeding the backslashed pattern in directly.
+ *
+ * The conversion is win32-ONLY because on POSIX a backslash is a legitimate
+ * escape (`src/\*.ts` = a file literally named `*.ts`); rewriting it there
+ * would silently change what the pattern means. `platform` is injected so both
+ * branches are unit-testable from either host — the shape
+ * `utils/win32-command.ts` uses.
+ */
+function toGlobSeparators(pattern, platform) {
+    return platform === 'win32' ? pattern.replaceAll('\\', '/') : pattern;
+}
 /** Expand ONE pattern to its lexicographically sorted match list. */
-async function expandPattern(pattern, ignore) {
-    const matched = await fastGlob([pattern], { ignore });
+async function expandPattern(pattern, ignore, platform) {
+    const normalized = toGlobSeparators(pattern, platform);
+    const matched = await fastGlob([normalized], { ignore: ignoreFor(normalized, ignore) });
     return matched.sort();
 }
-export const globToEntryPoints = async (_entryPoints, ignore = []) => {
+export const globToEntryPoints = async (_entryPoints, ignore = [], platform = process.platform) => {
     if (_entryPoints === undefined)
         return undefined;
-    const fullIgnore = [...DEFAULT_IGNORE, ...ignore];
+    // The ignore list is fed to the same matcher, so it needs the same
+    // treatment — a backslashed `--exclude` silently excludes nothing.
+    const fullIgnore = [...DEFAULT_IGNORE, ...ignore.map((p) => toGlobSeparators(p, platform))];
     if (typeof _entryPoints === 'string') {
-        return await expandPattern(_entryPoints, fullIgnore);
+        return await expandPattern(_entryPoints, fullIgnore, platform);
     }
     if (Array.isArray(_entryPoints)) {
         // Per-pattern expansion (not one combined fast-glob call): the
@@ -58,7 +114,7 @@ export const globToEntryPoints = async (_entryPoints, ignore = []) => {
         const out = [];
         const seen = new Set();
         for (const pattern of _entryPoints) {
-            for (const matched of await expandPattern(pattern, fullIgnore)) {
+            for (const matched of await expandPattern(pattern, fullIgnore, platform)) {
                 if (!seen.has(matched)) {
                     seen.add(matched);
                     out.push(matched);
@@ -70,7 +126,7 @@ export const globToEntryPoints = async (_entryPoints, ignore = []) => {
     const entryPoints = {};
     for (const input in _entryPoints) {
         const output = _entryPoints[input];
-        for (const matched of await expandPattern(input, fullIgnore)) {
+        for (const matched of await expandPattern(input, fullIgnore, platform)) {
             entryPoints[matched] = output;
         }
     }

package/lib/utils/index.d.ts

@@ -5,5 +5,5 @@ export * from './runtime.js';
 export * from './merge.js';
 export { detectFreeGlobals } from './detect-free-globals.js';
 export { resolveGlobalsList, writeRegisterInjectFile } from './scan-globals.js';
-export { inlineStaticReads } from './inline-static-reads.js';
+export { inlineStaticReads, isAbsoluteFsPath } from './inline-static-reads.js';
 export { GJSIFY_VIRTUAL_PREFIX, isGjsifyVirtualModuleId } from './virtual-module-id.js';

package/lib/utils/index.js

@@ -5,5 +5,5 @@ export * from './runtime.js';
 export * from './merge.js';
 export { detectFreeGlobals } from './detect-free-globals.js';
 export { resolveGlobalsList, writeRegisterInjectFile } from './scan-globals.js';
-export { inlineStaticReads } from './inline-static-reads.js';
+export { inlineStaticReads, isAbsoluteFsPath } from './inline-static-reads.js';
 export { GJSIFY_VIRTUAL_PREFIX, isGjsifyVirtualModuleId } from './virtual-module-id.js';

package/lib/utils/inline-static-reads.d.ts

@@ -9,3 +9,33 @@ export declare function inlineStaticReads(src: string, sourceFilePath: string):
     contents: string;
     inlined: number;
 };
+/**
+ * Is `v` an absolute filesystem path on `platform`?
+ *
+ * This is the last gate before a resolved expression is read from disk, and it
+ * used to be `v.startsWith('/')`. That is the right test for exactly one
+ * platform. On Windows every path this evaluator produces is `C:\…` — both
+ * documented compositions land there:
+ *
+ *     readFileSync(fileURLToPath(new URL('./x.txt', import.meta.url)), 'utf8')
+ *     readdirSync(path.join(__dirname))
+ *
+ * so both returned `undefined` and the call was left un-inlined. Silently: no
+ * warning, no error, just a bundle that keeps a runtime `readFileSync` against
+ * a build-site path and throws ENOENT the moment it is moved — which is the one
+ * failure this whole module exists to prevent (see the header). It also means
+ * the same source could bundle to DIFFERENT bytes on Windows than on Linux.
+ *
+ * Measured on win32 x64: the four `new URL(…)` patterns inline there correctly
+ * (the URL branch above never went through this gate); only the two that reduce
+ * to a path STRING were affected. No call site in this repo composes them
+ * inline today — every one goes through an intermediate variable, which the
+ * evaluator cannot follow on any platform — so no committed bundle is known to
+ * differ. This closes the gap before it opens.
+ *
+ * `platform` is injected and the branches use `path.win32`/`path.posix`
+ * explicitly, so both are exercised from either host — the same shape
+ * `extractPackageSpec` and `utils/entry-points.ts` use. On POSIX
+ * `posix.isAbsolute` IS `startsWith('/')`, so behaviour there is unchanged.
+ */
+export declare function isAbsoluteFsPath(v: string, platform?: string): boolean;

package/lib/utils/inline-static-reads.js

@@ -42,7 +42,7 @@
 // `import.meta.url` rewriter still applies as a fallback.
 import * as acorn from 'acorn';
 import * as walk from 'acorn-walk';
-import { dirname, join, resolve, basename, relative, extname } from 'node:path';
+import { dirname, join, resolve, basename, relative, extname, posix, win32 } from 'node:path';
 import { fileURLToPath, pathToFileURL } from 'node:url';
 import { existsSync, readFileSync, readdirSync, statSync } from 'node:fs';
 /**
@@ -287,10 +287,42 @@ function evalPathExpr(node, ctx) {
         return undefined;
     if (v.startsWith('file://'))
         return fileURLToPath(v);
-    if (v.startsWith('/'))
+    if (isAbsoluteFsPath(v))
         return v;
     return undefined;
 }
+/**
+ * Is `v` an absolute filesystem path on `platform`?
+ *
+ * This is the last gate before a resolved expression is read from disk, and it
+ * used to be `v.startsWith('/')`. That is the right test for exactly one
+ * platform. On Windows every path this evaluator produces is `C:\…` — both
+ * documented compositions land there:
+ *
+ *     readFileSync(fileURLToPath(new URL('./x.txt', import.meta.url)), 'utf8')
+ *     readdirSync(path.join(__dirname))
+ *
+ * so both returned `undefined` and the call was left un-inlined. Silently: no
+ * warning, no error, just a bundle that keeps a runtime `readFileSync` against
+ * a build-site path and throws ENOENT the moment it is moved — which is the one
+ * failure this whole module exists to prevent (see the header). It also means
+ * the same source could bundle to DIFFERENT bytes on Windows than on Linux.
+ *
+ * Measured on win32 x64: the four `new URL(…)` patterns inline there correctly
+ * (the URL branch above never went through this gate); only the two that reduce
+ * to a path STRING were affected. No call site in this repo composes them
+ * inline today — every one goes through an intermediate variable, which the
+ * evaluator cannot follow on any platform — so no committed bundle is known to
+ * differ. This closes the gap before it opens.
+ *
+ * `platform` is injected and the branches use `path.win32`/`path.posix`
+ * explicitly, so both are exercised from either host — the same shape
+ * `extractPackageSpec` and `utils/entry-points.ts` use. On POSIX
+ * `posix.isAbsolute` IS `startsWith('/')`, so behaviour there is unchanged.
+ */
+export function isAbsoluteFsPath(v, platform = process.platform) {
+    return (platform === 'win32' ? win32 : posix).isAbsolute(v);
+}
 function evalExpr(node, ctx) {
     if (!node)
         return undefined;

package/lib/utils/scan-globals.js

@@ -14,7 +14,7 @@ import { writeFile, mkdir } from 'node:fs/promises';
 import { existsSync } from 'node:fs';
 import { createHash } from 'node:crypto';
 import { join } from 'node:path';
-import { GJS_GLOBALS_MAP, GJS_GLOBALS_GROUPS, REVERSE_BRIDGE_NATIVE_OVERRIDE_IDENTS } from '@gjsify/resolve-npm/globals-map';
+import { GJS_GLOBALS_MAP, GJS_GLOBALS_GROUPS, REVERSE_BRIDGE_NATIVE_OVERRIDE_IDENTS, } from '@gjsify/resolve-npm/globals-map';
 import { ALIASES_WEB_FOR_GJS } from '@gjsify/resolve-npm';
 const GLOBALS_MAP = GJS_GLOBALS_MAP;
 const GLOBALS_GROUPS = GJS_GLOBALS_GROUPS;

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@gjsify/rolldown-plugin-gjsify",
-    "version": "0.26.1",
+    "version": "0.27.1",
     "description": "Rolldown / Rollup / Vite plugin orchestrator for GJS, Node, and Browser targets",
     "type": "module",
     "main": "lib/index.js",
@@ -33,9 +33,9 @@
         "lib"
     ],
     "scripts": {
-        "clear": "rm -rf lib tsconfig.tsbuildinfo || exit 0",
+        "clear": "gjsify clear lib tsconfig.tsbuildinfo",
         "check": "gjsify tsc --noEmit",
-        "build": "tsc"
+        "build": "gjsify tsc"
     },
     "repository": {
         "type": "git",
@@ -55,11 +55,11 @@
     ],
     "license": "MIT",
     "dependencies": {
-        "@gjsify/console": "^0.26.1",
-        "@gjsify/resolve-npm": "^0.26.1",
-        "@gjsify/rolldown-plugin-deepkit": "^0.26.1",
-        "@gjsify/rolldown-plugin-pnp": "^0.26.1",
-        "@gjsify/vite-plugin-blueprint": "^0.26.1",
+        "@gjsify/console": "^0.27.1",
+        "@gjsify/resolve-npm": "^0.27.1",
+        "@gjsify/rolldown-plugin-deepkit": "^0.27.1",
+        "@gjsify/rolldown-plugin-pnp": "^0.27.1",
+        "@gjsify/vite-plugin-blueprint": "^0.27.1",
         "@rollup/pluginutils": "^5.4.0",
         "acorn": "^8.17.0",
         "acorn-walk": "^8.3.5",
@@ -68,7 +68,7 @@
         "sass": "^1.101.0"
     },
     "peerDependencies": {
-        "@gjsify/lightningcss-native": "^0.26.1",
+        "@gjsify/lightningcss-native": "^0.27.1",
         "rolldown": "^1.1.4"
     },
     "peerDependenciesMeta": {