@gjsify/rolldown-native 0.4.42 → 0.4.44

package/README.md

@@ -0,0 +1,35 @@
+# @gjsify/rolldown-native
+
+A native Rust cdylib + Vala/GObject bridge that wraps the Rust `rolldown` bundler and exposes it to GJS via `gi://`. This is the default bundler engine used by `gjsify build` under GJS — npm's `rolldown` is an N-API addon that cannot load in GJS, so this bridge is how gjsify bundles without a Node runtime. Includes a complete plugin bridge (`bundleWithPlugins`) for load, transform, resolveId, and render-chunk hooks. Ships prebuilt `.so` + `.typelib` for Linux.
+
+Part of the [gjsify](https://github.com/gjsify/gjsify) project — Node.js and Web APIs for GJS (GNOME JavaScript).
+
+## Installation
+
+```bash
+gjsify install @gjsify/rolldown-native
+```
+
+## Usage
+
+```typescript
+import { hasNativeRolldown, bundle, bundleWithPlugins } from '@gjsify/rolldown-native';
+
+if (hasNativeRolldown()) {
+    // Simple bundle
+    const result = bundle({
+        input: [{ import: 'src/index.ts' }],
+        format: 'esm',
+        minify: false,
+    });
+    for (const item of result.output) {
+        if (item.type === 'chunk') console.log(item.fileName, item.code.length, 'bytes');
+    }
+}
+```
+
+Under normal usage `@gjsify/rolldown-native` is consumed automatically by the gjsify CLI (`gjsify build`) — direct use is only needed when embedding the bundler in custom build tooling.
+
+## License
+
+MIT

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@gjsify/rolldown-native",
-    "version": "0.4.42",
+    "version": "0.4.44",
     "description": "Phase D-2 POC: Vala/GObject + Rust cdylib bridge to rolldown for GJS. Wraps `rolldown::Bundler::generate()` (async, tokio) in a per-call current-thread runtime so JS sees a sync `bundle()` call. JSON-encoded BundlerOptions in, JSON-encoded BundleOutput out — the boundary stays small even though rolldown's option surface is enormous. POC scope: no JS plugins (Phase B), no watch/HMR, no incremental builds. Companion to `@gjsify/lightningcss-native`; together they remove the last two Rust-crate runtime blockers from the gjsify build pipeline (Phase D-3 unblock).",
     "type": "module",
     "main": "lib/esm/index.js",
@@ -47,7 +47,7 @@
         "@girs/gobject-2.0": "2.88.0-4.0.4"
     },
     "devDependencies": {
-        "@gjsify/cli": "^0.4.42",
+        "@gjsify/cli": "^0.4.44",
         "@types/node": "^25.9.1",
         "typescript": "^6.0.3"
     },

package/src/vala/gjsify-rolldown-glue.c

@@ -175,9 +175,18 @@ gjsify_rolldown_glue_session_take_request_payload (BundleSession *session,
   if (session == NULL) return NULL;
   size_t len = 0;
   uint8_t *buf = gjsify_rolldown_session_take_request_payload (session, req_id, &len);
-  if (buf == NULL || len == 0) return NULL;
+  /* NULL buf = no payload was stashed for this req_id (genuine miss) → NULL.
+   * A non-NULL buf with len == 0 is an EMPTY-but-present payload (e.g. the
+   * `transform` hook on rolldown's virtual `\0rolldown/empty.js` module, whose
+   * code is ""). It MUST yield an empty GBytes, NOT NULL — otherwise the JS
+   * adapter reads `take_request_payload() === null` and throws "missing payload
+   * bytes", which is exactly what broke the CLI self-build. Don't fold len==0
+   * into the miss case. */
+  if (buf == NULL) return NULL;
   /* Copy into GLib heap and free the Rust allocation immediately so
-   * GBytes refcount/lifetime stays inside the GLib side. */
+   * GBytes refcount/lifetime stays inside the GLib side. g_bytes_new copies
+   * `len` bytes; for len == 0 it never dereferences `buf`, so the Rust
+   * dangling-but-aligned zero-length pointer is safe here. */
   GBytes *out = g_bytes_new (buf, len);
   gjsify_rolldown_session_free_payload (buf, len);
   return out;