rwsdk 1.0.0 → 1.0.1

package/dist/runtime/render/preloads.js

@@ -1,5 +1,8 @@
 import { jsx as _jsx, Fragment as _Fragment } from "react/jsx-runtime";
 import { getManifest } from "../lib/manifest.js";
+// context(justinvdm, 2026-03-15): See toManifestKey in stylesheets.tsx for
+// why we strip the leading slash.
+const toManifestKey = (id) => (id.startsWith("/") ? id.slice(1) : id);
 export function findScriptForModule(id, manifest) {
     const visited = new Set();
     function find(id) {
@@ -7,7 +10,7 @@ export function findScriptForModule(id, manifest) {
             return;
         }
         visited.add(id);
-        const manifestEntry = manifest[id];
+        const manifestEntry = manifest[toManifestKey(id)];
         if (!manifestEntry) {
             return;
         }

package/dist/runtime/render/stylesheets.js

@@ -1,5 +1,11 @@
 import { jsx as _jsx, Fragment as _Fragment } from "react/jsx-runtime";
 import { getManifest } from "../lib/manifest.js";
+// context(justinvdm, 2026-03-15): Vite's client manifest uses keys without
+// a leading slash (e.g. "src/app/pages/Welcome.tsx"), but our module IDs in
+// scriptsToBeLoaded use Vite-style leading-slash paths (e.g.
+// "/src/app/pages/Welcome.tsx") from normalizeModulePath. We strip the
+// leading slash here so the lookup succeeds.
+const toManifestKey = (id) => (id.startsWith("/") ? id.slice(1) : id);
 const findCssForModule = (scriptId, manifest) => {
     const css = new Set();
     const visited = new Set();
@@ -8,7 +14,7 @@ const findCssForModule = (scriptId, manifest) => {
             return;
         }
         visited.add(id);
-        const entry = manifest[id];
+        const entry = manifest[toManifestKey(id)];
         if (!entry) {
             return;
         }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rwsdk",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "Build fast, server-driven webapps on Cloudflare with SSR, RSC, and realtime",
   "type": "module",
   "bin": {