@gjsify/cli 0.48.0 → 0.49.0

package/lib/actions/build.js

@@ -630,7 +630,7 @@ export class BuildAction {
             throw new Error('gjsify build: an .html entry needs an explicit --outfile ' +
                 '(e.g. --outfile dist-app/app.js); the emitted index.html is written beside it.');
         }
-        const { consoleShim, globals, dialect } = this.configData;
+        const { consoleShim, globals, dialect, giRenderer } = this.configData;
         const userExternal = Array.isArray(userBundler.external) ? userBundler.external : undefined;
         const userBanner = typeof userBundler.output?.banner === 'string' ? userBundler.output.banner : undefined;
         const pluginOpts = {
@@ -641,6 +641,7 @@ export class BuildAction {
             reflection: typescript?.reflection,
             consoleShim,
             ...(dialect !== undefined ? { dialect } : {}),
+            ...(giRenderer === true ? { giRenderer: true } : {}),
             ...(aliases ? { aliases } : {}),
             ...(opts.preserveDefaultExport ? { preserveDefaultExport: true } : {}),
             ...(opts.toolchainAnchor !== undefined ? { toolchainAnchor: opts.toolchainAnchor } : {}),

package/lib/commands/build.js

@@ -112,6 +112,10 @@ export const buildCommand = {
             description: "The dialect the SOURCE is written in. 'react-native' aliases 'react-native' onto '@gjsify/react-native' and fails the build on an import whose ADR 0032 support-table status is not supported/partial. GJS and Node app builds. This is NOT gjsify.runtimes['react-native'], which declares the runtime a package RUNS on — the two answer opposite questions.",
             type: 'string',
             choices: [...SOURCE_DIALECTS],
+        })
+            .option('gi-renderer', {
+            description: "Resolve `gi://Ns?version=X` to the target's widget renderer instead of an empty module (ADR 0034 stage 9): --app browser answers gi://Adw and gi://Gtk out of @gjsify/adwaita-web, --app nativescript out of @gjsify/adwaita-nativescript. A namespace with no renderer, and a ?version= the renderer's vocabulary was not generated against, both FAIL the build by name. Off by default — a gi:// import on those targets is usually a GJS-only code path pulled in transitively.",
+            type: 'boolean',
         })
             .option('console-shim', {
             description: 'Inject a console shim into GJS builds for clean output without the GLib prefix and with working ANSI colors. Use --no-console-shim to disable. Only applies to GJS app builds.',

package/lib/commands/install.js

@@ -23,7 +23,7 @@ import { spawnSync } from 'node:child_process';
 import { forceExit } from '../utils/force-exit.js';
 import { discoverWorkspaces } from '@gjsify/workspace';
 import { buildInstallCommand, detectPackageManager, runMinimalChecks } from '../utils/check-system-deps.js';
-import { detectNativePackages } from '../utils/detect-native-packages.js';
+import { detectHostLibc, detectNativePackages, muslPrebuildFallbacks } from '../utils/detect-native-packages.js';
 import { buildLauncherShims, buildNativeEnvPreamble } from '../utils/bin-shim.js';
 import { installPackages, makeProgressReporter } from '../utils/install-backend.js';
 import { atomicWriteStrict } from '../utils/install-cache-fs.js';
@@ -1339,6 +1339,26 @@ async function runPostInstallChecks(args) {
             console.log(`  • ${pkg.name}`);
         }
         console.log('\nUse `gjsify run <bundle>` to launch with LD_LIBRARY_PATH/GI_TYPELIB_PATH set.');
+        // The install is the ONLY moment this is knowable: the libc axis is decided
+        // here, the failure it predicts happens in another process, days later, and
+        // names something else entirely (see `muslPrebuildFallbacks`). The list is
+        // the point — it is what lets a later `Error relocating` line be matched to
+        // a package.
+        const fellBack = muslPrebuildFallbacks(detectHostLibc(process.platform), native);
+        if (fellBack.length > 0) {
+            console.warn(`\nWarning: musl host — ${fellBack.length} of ${native.length} package(s) ship no \`-musl\`` +
+                ' prebuild, so the\n  default (glibc) build was used:');
+            for (const name of fellBack)
+                console.warn(`    ${name}`);
+            console.warn('  Most of these run anyway: a bridge that links only GLib records no libc at all.\n' +
+                '  One that links glibc loads too — musl aliases `libc.so.6` to itself — and then\n' +
+                '  fails at dlopen on its first glibc-only symbol:\n' +
+                '    Error relocating <prebuild>.so: <symbol>: symbol not found\n' +
+                '  A bridge lost that way is silently absent from the next build rather than\n' +
+                '  reported, so the first symptom can be an unrelated-looking bundler error\n' +
+                '  (`Could not load <file>` from rolldown, for the CSS bridge). Nothing to\n' +
+                '  install: no `-musl` package is published for any target yet.');
+        }
     }
     maybeInstallGitHooks();
 }

package/lib/commands/upgrade.js

@@ -12,11 +12,15 @@
 //      matching packages automatically without prompting; same selection
 //      logic as above but no UI loop.
 //
-//   3. `--align`: offline consistency-only mode. Finds deps declared at
-//      multiple ranges across the workspace and proposes a single range
-//      (the highest declared) — no registry calls.
+//   3. `--align`: offline repair mode. Finds deps declared at multiple ranges
+//      across the workspace and proposes a single range (the highest declared)
+//      — no registry calls. With `--exact` it repairs the second question too:
+//      a dep every manifest declares identically as `^4.1.0` is consistent and
+//      still carries an operator, so the operator goes as well.
 //
-//   4. `--check`: CI gate. Exits non-zero when any inconsistency exists.
+//   4. `--check`: CI gate. Exits non-zero when any inconsistency exists; with
+//      `--exact`, also when any matched declaration carries a range operator.
+//      Whatever `--check` rejects, `--align` with the same flags repairs.
 //
 // Filters:
 //
@@ -36,7 +40,7 @@ import { parse } from '@gjsify/semver';
 import { DEFAULT_REGISTRY, fetchPackument, parseNpmrc } from '@gjsify/npm-registry';
 import { discoverWorkspaces, filterWorkspaces } from '@gjsify/workspace';
 import { findWorkspaceRoot } from '../utils/workspace-root.js';
-import { groupByDependency, findInconsistencies, } from '../utils/dep-aggregation.js';
+import { groupByDependency, findInconsistencies, isInconsistent, } from '../utils/dep-aggregation.js';
 export const upgradeCommand = {
     command: 'upgrade',
     description: 'Workspace-aware dependency upgrades. Walks every package.json in the monorepo, groups by dep, flags inconsistencies. `--latest` / `--minor` / `--patch` for bulk-mode, `--align` for offline consistency-only mode, `--check` for CI drift detection.',
@@ -71,7 +75,7 @@ export const upgradeCommand = {
             type: 'string',
         })
             .option('align', {
-            description: 'Offline consistency mode: find deps declared at multiple ranges across the workspace and align them to the highest. No registry calls.',
+            description: 'Offline repair mode: find deps declared at multiple ranges across the workspace and align them to the highest. With `--exact`, also drop the range operator from declarations that already agree. No registry calls.',
             type: 'boolean',
             default: false,
         })
@@ -81,7 +85,7 @@ export const upgradeCommand = {
             default: false,
         })
             .option('exact', {
-            description: 'Pin without a range operator. When writing, emits `1.2.3` instead of `^1.2.3`; with `--check`, fails on any matched dep that carries one. Pair with `--filter` — a repository-wide exactness check fails on every ordinary caret dep by design.',
+            description: 'Pin without a range operator. When writing, emits `1.2.3` instead of `^1.2.3`; with `--check`, fails on any matched dep that carries one; with `--align`, repairs exactly that. Pair with `--filter` — a repository-wide exactness run touches every ordinary caret dep by design.',
             type: 'boolean',
             default: false,
         })
@@ -348,22 +352,63 @@ function runCheckMode(groups, exact = false) {
             console.error(`    ${range.padEnd(16)} — ${holders.join(', ')}`);
         }
     }
-    console.error(`\nFix: run \`gjsify upgrade --align\` (offline; aligns each dep to its highest declared range).`);
+    console.error(exact
+        ? `\nFix: run \`gjsify upgrade --align --exact\` (offline; aligns each dep to its highest declared version and drops the operator).`
+        : `\nFix: run \`gjsify upgrade --align\` (offline; aligns each dep to its highest declared range).`);
     process.exit(1);
 }
+/**
+ * The groups `--align` has work on.
+ *
+ * Inconsistency is the whole question for a bare `--align`: a dep every manifest declares
+ * identically is done. `--exact` asks a second one, and the two do not overlap — a tree
+ * where every manifest says `^4.1.0` is perfectly consistent and carries an operator on
+ * every one of those declarations, which is precisely what `--check --exact` rejects.
+ *
+ * Selecting on inconsistency alone therefore made the repair that `--check --exact`'s own
+ * failure message names answer `nothing to do` to the tree it was pointed at: the gate
+ * demanded a property the fix could not deliver, cheerfully. Measured on bauplaner's five
+ * `@girs/*` declarations, all five `^4.1.0` and all five consistent.
+ */
+function alignTargets(groups, exact) {
+    if (!exact)
+        return findInconsistencies(groups);
+    return groups.filter((g) => isInconsistent(g) || g.occurrences.some((o) => o.prefix !== ''));
+}
+/**
+ * A repair that silently skipped part of its job must not report success.
+ *
+ * The loop that produces is gate red → repair "done" → gate red, where the second red
+ * reads as if the repair had never run. `^1.x` is the shape that lands here: `--check
+ * --exact` flags the operator, and no single version can be read out of the range to pin
+ * it at, so there is nothing to write and the CLI says which deps those are instead.
+ */
+function reportUnrepairable(groups) {
+    console.error(`\ngjsify upgrade --align: ${groups.length} dep(s) left unrepaired — no version to align on:\n`);
+    for (const g of groups) {
+        console.error(`  ${ANSI.bold}${g.name}${ANSI.reset}  ${[...g.declaredRanges].join(', ')}`);
+    }
+    console.error(`\nThose ranges name no single version. Edit them by hand, or resolve one with \`--latest\`.`);
+    return process.exit(1);
+}
 function runAlignMode(groups, args) {
-    const inconsistencies = findInconsistencies(groups);
-    if (inconsistencies.length === 0) {
-        console.log(`gjsify upgrade --align: nothing to do. ${groups.length} dep(s) already consistent.`);
+    const exact = args.exact ?? false;
+    const targets = alignTargets(groups, exact);
+    if (targets.length === 0) {
+        console.log(`gjsify upgrade --align: nothing to do. ${groups.length} dep(s) already consistent` +
+            (exact ? `, every declaration pinned exactly.` : `.`));
         return;
     }
-    // For each inconsistency, the alignment target is the highest declared version
-    // — preserve the prefix of the dominant occurrence so the range shape doesn't
-    // mutate (caret stays caret, tilde stays tilde).
+    // For each target, the alignment version is the highest declared one — preserve the
+    // prefix of the dominant occurrence so the range shape doesn't mutate (caret stays
+    // caret, tilde stays tilde). Under `--exact` the prefix is dropped, in `targetRange`.
     const updates = [];
-    for (const g of inconsistencies) {
-        if (!g.highestVersion)
+    const unrepairable = [];
+    for (const g of targets) {
+        if (!g.highestVersion) {
+            unrepairable.push(g);
             continue;
+        }
         // Pick a prefix: use the prefix of the dominant range; if dominant has
         // no prefix, default to "^" (the npm-cli default).
         const dominantOcc = g.occurrences.find((o) => o.currentRange === g.dominantRange);
@@ -375,21 +420,24 @@ function runAlignMode(groups, args) {
             occurrences: g.occurrences.map((o) => ({ ...o, prefix })),
         });
     }
-    if (updates.length === 0) {
-        console.log('gjsify upgrade --align: inconsistencies present but no parseable target version. No-op.');
-        return;
-    }
-    console.log(`gjsify upgrade --align: aligning ${updates.length} inconsistent dep(s) to their highest declared version:\n`);
-    for (const u of updates) {
-        const newPrefix = u.occurrences[0]?.prefix ?? '^';
-        console.log(`  ${u.name.padEnd(28)}  ranges: ${[...u.declaredRanges].join(', ')}  →  ${targetRange(newPrefix, u.latestVersion, args.exact ?? false)}`);
-    }
-    if (args.dryRun) {
-        console.log('\n[gjsify upgrade --align] --dry-run: no files changed.');
-        return;
+    if (updates.length > 0) {
+        console.log(exact
+            ? `gjsify upgrade --align --exact: pinning ${updates.length} dep(s) to their highest declared version, without a range operator:\n`
+            : `gjsify upgrade --align: aligning ${updates.length} inconsistent dep(s) to their highest declared version:\n`);
+        for (const u of updates) {
+            const newPrefix = u.occurrences[0]?.prefix ?? '^';
+            console.log(`  ${u.name.padEnd(28)}  ranges: ${[...u.declaredRanges].join(', ')}  →  ${targetRange(newPrefix, u.latestVersion, exact)}`);
+        }
+        if (args.dryRun) {
+            console.log('\n[gjsify upgrade --align] --dry-run: no files changed.');
+        }
+        else {
+            const files = applyToFiles(updates, exact);
+            console.log(`\n✏️  updated ${updates.length} dep(s) across ${files} package.json file(s).`);
+        }
     }
-    const files = applyToFiles(updates, args.exact);
-    console.log(`\n✏️  updated ${updates.length} dep(s) across ${files} package.json file(s).`);
+    if (unrepairable.length > 0)
+        return reportUnrepairable(unrepairable);
 }
 // ─── Registry resolution (group-aware) ─────────────────────────────────
 async function resolveCandidateGroups(groups, npmrc, verbose, mode) {

package/lib/config.js

@@ -5,6 +5,7 @@ import { pathToFileURL } from 'node:url';
 import { isGjs, hostRuntime } from '@gjsify/rolldown-plugin-gjsify/runtime';
 import { buildAppForRuntime } from './utils/runtimes.js';
 import { DIALECT_APPS, isSourceDialect, SOURCE_DIALECTS } from '@gjsify/rolldown-plugin-gjsify';
+import { GI_RENDERER_APPS } from '@gjsify/resolve-npm';
 /**
  * Does the failed `import()` of a config look like a MODULE-RESOLUTION failure
  * (the config imports something GJS's ESM loader can't resolve for an external
@@ -269,6 +270,8 @@ export class Config {
         configData.exclude = cliArgs.exclude || [];
         if (cliArgs.consoleShim !== undefined)
             configData.consoleShim = cliArgs.consoleShim;
+        if (cliArgs.giRenderer !== undefined)
+            configData.giRenderer = cliArgs.giRenderer;
         // `--dialect` narrows here rather than at the call site. yargs `choices`
         // already rejects an unknown value typed on the command line, but a
         // `gjsify.dialect` in package.json or `.gjsifyrc.*` never passes through
@@ -303,6 +306,16 @@ export class Config {
                 `It composes on ${[...DIALECT_APPS].join(' and ')} only. ` +
                 'Drop the dialect, or build one of those targets.');
         }
+        // Same rule for the `gi://` arm, and the same reason: `--gi-renderer --app gjs`
+        // would parse, resolve and compose nothing, so the flag would be accepted and
+        // ignored. On `gjs` and `node` the specifier is already answered — natively and
+        // through `requireGi` — so there is nothing for a renderer to substitute for.
+        if (configData.giRenderer === true && !GI_RENDERER_APPS.includes(configData.app)) {
+            throw new Error(`gjsify build: --gi-renderer has no effect on --app ${configData.app}. ` +
+                `It composes on ${GI_RENDERER_APPS.join(' and ')} only — the targets with no GObject ` +
+                'introspection to answer `gi://` with. `--app gjs` resolves it natively and `--app node` ' +
+                'through @gjsify/node-gi, so neither needs a widget renderer standing in for it.');
+        }
         if (cliArgs.globals !== undefined)
             configData.globals = cliArgs.globals;
         // Fallback applied post-merge (not as a yargs `default:`) so a

package/lib/types/cli-build-options.d.ts

@@ -36,6 +36,12 @@ export interface CliBuildOptions {
      * whatever was typed, and the narrowing happens once, where the value is read.
      */
     dialect?: string;
+    /**
+     * Resolve `gi://Ns?version=X` to the target's widget renderer instead of an empty
+     * module — `--gi-renderer` (ADR 0034 stage 9). `browser` and `nativescript` targets.
+     * Default: unset; see `ConfigData.giRenderer` for why it is opt-in.
+     */
+    giRenderer?: boolean;
     /**
      * Comma-separated global identifiers the code needs, e.g.
      * `"fetch,Buffer,process,URL,crypto"`. Each maps to the corresponding

package/lib/types/config-data.d.ts

@@ -96,6 +96,20 @@ export interface ConfigData {
      * see the header of `SourceDialect`.
      */
     dialect?: SourceDialect;
+    /**
+     * Resolve `gi://Ns?version=X` to the target's widget renderer rather than to an
+     * empty module (ADR 0034 stage 9). `--app browser` answers out of
+     * `@gjsify/adwaita-web`, `--app nativescript` out of `@gjsify/adwaita-nativescript`;
+     * `GI_RENDERERS` in `@gjsify/resolve-npm` is the table, and a target with no row
+     * there has no arm. Default: unset.
+     *
+     * Opt-in, never inferred: a `gi://` import reaching one of those targets today is
+     * usually a GJS-only code path pulled in transitively, which the empty module
+     * silences on purpose. On by default it would pull a widget toolkit into bundles
+     * that never named one, and turn every unanswerable namespace from a silent stub
+     * into a hard build failure.
+     */
+    giRenderer?: boolean;
     /** Comma-separated global identifiers to register. Format: see CliBuildOptions. */
     globals?: string;
     /**

package/lib/utils/detect-native-packages.d.ts

@@ -233,6 +233,37 @@ export declare function resolveHostLibc(input: {
  * reach it.
  */
 export declare function detectHostLibc(platform: string): HostLibc | null;
+/**
+ * The packages a musl host had to take the DEFAULT prebuild of, because they ship
+ * no `-musl` directory — the fallback {@link hostPlatformTokens} deliberately
+ * allows, named so a caller can report it. Returns names and prints nothing: this
+ * module resolves, and `libc` is a parameter for the same reason it is on every
+ * other function here (there is no musl runner in this repo's CI, so an injected
+ * `libc: 'musl'` is the only way the branch executes).
+ *
+ * Why a fallback that mostly WORKS is worth naming. musl's loader resolves
+ * `libc.so.6`/`libm.so.6` to itself, so a glibc-linked prebuild loads — and a
+ * bridge that records no libc at all then runs correctly, which is why the
+ * fallback exists rather than resolving to null. The one that is NOT agnostic dies
+ * at `dlopen` on its first glibc-only symbol, far from its cause. Measured on a
+ * OnePlus 6 (postmarketOS v26.06, musl 1.2.6, aarch64, gjs 1.88.1) against the
+ * published 0.48.0 train: nine of ten prebuilds loaded, while
+ * `@gjsify/lightningcss-native-linux-arm64` answered `gnu_get_libc_version: symbol
+ * not found`. `gjsify install` had printed "System dependencies OK", and the first
+ * symptom was rolldown reporting `Could not load src/application.css` — the CSS
+ * bridge silently absent from the bundle. Nothing in that chain names libc, which
+ * is what makes the report worth more than the failure.
+ *
+ * Membership goes through {@link parsePlatformToken}, not the suffix constant, so
+ * this does not become a second reader of the libc half of the token grammar —
+ * `darwin-arm64-musl` is a malformed token rather than a musl build, and only the
+ * grammar knows that.
+ *
+ * TODO(open-todos: `-musl` prebuild package is published): naming the fallback is
+ * not fixing it. No `-musl` target is published for any bridge, so on a musl host
+ * this reports every prebuild in the tree and there is nothing to fall back FROM.
+ */
+export declare function muslPrebuildFallbacks(libc: HostLibc | null, packages: readonly NativePackage[]): string[];
 /**
  * The environment-variable name the host's dynamic loader consults for an
  * additional shared-library search path, plus the separator its search paths

package/lib/utils/detect-native-packages.js

@@ -22,7 +22,7 @@
 // win32 AND musl branches unit-testable from a glibc Linux host. The host values
 // are read only at the outermost call site, as a default.
 import { readdirSync, existsSync } from 'node:fs';
-import { join, resolve } from 'node:path';
+import { basename, join, resolve } from 'node:path';
 import { readPackageJson } from './pkg-json.js';
 import { composeDyldFallback, systemGiLibraryDirs } from './system-gi.js';
 /**
@@ -500,6 +500,42 @@ export function detectHostLibc(platform) {
     const muslLoaderPresent = existsSync('/lib') && readdirSync('/lib').some((f) => f.startsWith('ld-musl-'));
     return resolveHostLibc({ platform, glibcVersionRuntime, muslLoaderPresent });
 }
+/**
+ * The packages a musl host had to take the DEFAULT prebuild of, because they ship
+ * no `-musl` directory — the fallback {@link hostPlatformTokens} deliberately
+ * allows, named so a caller can report it. Returns names and prints nothing: this
+ * module resolves, and `libc` is a parameter for the same reason it is on every
+ * other function here (there is no musl runner in this repo's CI, so an injected
+ * `libc: 'musl'` is the only way the branch executes).
+ *
+ * Why a fallback that mostly WORKS is worth naming. musl's loader resolves
+ * `libc.so.6`/`libm.so.6` to itself, so a glibc-linked prebuild loads — and a
+ * bridge that records no libc at all then runs correctly, which is why the
+ * fallback exists rather than resolving to null. The one that is NOT agnostic dies
+ * at `dlopen` on its first glibc-only symbol, far from its cause. Measured on a
+ * OnePlus 6 (postmarketOS v26.06, musl 1.2.6, aarch64, gjs 1.88.1) against the
+ * published 0.48.0 train: nine of ten prebuilds loaded, while
+ * `@gjsify/lightningcss-native-linux-arm64` answered `gnu_get_libc_version: symbol
+ * not found`. `gjsify install` had printed "System dependencies OK", and the first
+ * symptom was rolldown reporting `Could not load src/application.css` — the CSS
+ * bridge silently absent from the bundle. Nothing in that chain names libc, which
+ * is what makes the report worth more than the failure.
+ *
+ * Membership goes through {@link parsePlatformToken}, not the suffix constant, so
+ * this does not become a second reader of the libc half of the token grammar —
+ * `darwin-arm64-musl` is a malformed token rather than a musl build, and only the
+ * grammar knows that.
+ *
+ * TODO(open-todos: `-musl` prebuild package is published): naming the fallback is
+ * not fixing it. No `-musl` target is published for any bridge, so on a musl host
+ * this reports every prebuild in the tree and there is nothing to fall back FROM.
+ */
+export function muslPrebuildFallbacks(libc, packages) {
+    if (libc !== 'musl')
+        return [];
+    const fellBack = packages.filter((pkg) => parsePlatformToken(basename(pkg.prebuildsDir)).libc !== 'musl');
+    return fellBack.map((pkg) => pkg.name);
+}
 /**
  * The environment-variable name the host's dynamic loader consults for an
  * additional shared-library search path, plus the separator its search paths

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@gjsify/cli",
-    "version": "0.48.0",
+    "version": "0.49.0",
     "description": "CLI for Gjsify",
     "type": "module",
     "main": "lib/index.js",
@@ -142,21 +142,21 @@
         "cli"
     ],
     "dependencies": {
-        "@gjsify/buffer": "^0.48.0",
-        "@gjsify/create-app": "^0.48.0",
-        "@gjsify/node-globals": "^0.48.0",
-        "@gjsify/node-polyfills": "^0.48.0",
-        "@gjsify/npm-registry": "^0.48.0",
-        "@gjsify/resolve-npm": "^0.48.0",
-        "@gjsify/rolldown-plugin-gjsify": "^0.48.0",
-        "@gjsify/vite-plugin-blueprint": "^0.48.0",
-        "@gjsify/rolldown-plugin-pnp": "^0.48.0",
-        "@gjsify/semver": "^0.48.0",
-        "@gjsify/tar": "^0.48.0",
-        "@gjsify/tsc": "^0.48.0",
-        "@gjsify/utils": "^0.48.0",
-        "@gjsify/web-polyfills": "^0.48.0",
-        "@gjsify/workspace": "^0.48.0",
+        "@gjsify/buffer": "^0.49.0",
+        "@gjsify/create-app": "^0.49.0",
+        "@gjsify/node-globals": "^0.49.0",
+        "@gjsify/node-polyfills": "^0.49.0",
+        "@gjsify/npm-registry": "^0.49.0",
+        "@gjsify/resolve-npm": "^0.49.0",
+        "@gjsify/rolldown-plugin-gjsify": "^0.49.0",
+        "@gjsify/vite-plugin-blueprint": "^0.49.0",
+        "@gjsify/rolldown-plugin-pnp": "^0.49.0",
+        "@gjsify/semver": "^0.49.0",
+        "@gjsify/tar": "^0.49.0",
+        "@gjsify/tsc": "^0.49.0",
+        "@gjsify/utils": "^0.49.0",
+        "@gjsify/web-polyfills": "^0.49.0",
+        "@gjsify/workspace": "^0.49.0",
         "acorn": "^8.17.0",
         "cosmiconfig": "^9.0.2",
         "get-tsconfig": "^4.14.0",
@@ -165,13 +165,13 @@
         "yargs": "^18.0.0"
     },
     "devDependencies": {
-        "@gjsify/unit": "^0.48.0",
+        "@gjsify/unit": "^0.49.0",
         "@types/yargs": "^17.0.35",
         "typescript": "^6.0.3"
     },
     "peerDependencies": {
-        "@gjsify/oxfmt-native": "^0.48.0",
-        "@gjsify/rolldown-native": "^0.48.0"
+        "@gjsify/oxfmt-native": "^0.49.0",
+        "@gjsify/rolldown-native": "^0.49.0"
     },
     "peerDependenciesMeta": {
         "@gjsify/oxfmt-native": {