solid-tag-runtime 0.0.4 → 0.0.5

package/ARCHITECTURE.md

@@ -916,3 +916,13 @@ Reason: attributes are useful across declarative HTML and DevTools but cannot un
 ### 0.0.4 — typing/test/documentation hardening
 
 Decision: publish the next package as `0.0.4` because `0.0.3` has already been published. `0.0.4` preserves the `0.0.3` runtime/HTML semantics while shipping the DOM-compatible HTML adapter declaration fixes, broader regression coverage, and updated feature documentation. No module-resolution, ownership, execution-backend, or cache-invalidation semantics change in this release.
+### 0.0.5 — fresh module identity after invalidation
+
+Decision: every execution-backend `create(code)` call must produce a fresh native ESM module identity, even when the generated source text is byte-for-byte identical to an earlier version. The `data:` backend now appends a monotonically increasing fragment to each generated URL. This matches the naturally unique URLs returned by `URL.createObjectURL()` and prevents the browser/Node ESM cache from returning a previously evaluated module after `invalidate()`, `update()`, or `defineModule()` replacement.
+
+Reason: replacing a host namespace correctly invalidated its dependents in the runtime graph, but a deterministic `data:` URL could recreate the exact same URL for the host bridge and dependent source. Native ESM caches by URL, so the old evaluation was reused and dependents continued to observe stale host exports.
+
+Invariant: invalidation must result in a fresh executable module identity on the next compile/import. Cache invalidation is not complete if the execution backend can recreate an already-evaluated URL.
+
+Regression coverage: host-module replacement must update already-imported dependents, and explicit `runtime.invalidate()` must cause a side-effecting module to evaluate again on the next import.
+

package/README.md

@@ -272,7 +272,7 @@ solid-module                → infer from module/src extension
 
 ### Addition-only observation
 
-Observation remains addition-only in `0.0.4`.
+Observation remains addition-only in `0.0.5`.
 
 Changing the source/attributes of an already owned script or removing it from the DOM does not implicitly update/delete the corresponding runtime module. Use `runtime.update()` / `runtime.invalidate()` for explicit module lifecycle changes.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "solid-tag-runtime",
-  "version": "0.0.4",
+  "version": "0.0.5",
   "description": "Runtime module system for JSX modules compiled with solid-tag and executed through @solidjs/html",
   "type": "module",
   "exports": {

package/src/url-backend.js

@@ -23,10 +23,17 @@ export function createBlobModuleUrlBackend() {
 }
 
 export function createDataModuleUrlBackend() {
+  let sequence = 0;
+
   return {
     kind: "data",
     create(code) {
-      return `data:text/javascript;charset=utf-8,${encodeURIComponent(code)}`;
+      // Native ESM caches modules by URL. Recreating the same data: URL after
+      // invalidation would otherwise return the previously evaluated module.
+      // Give every backend create() call a fresh module identity, matching the
+      // naturally unique identity of URL.createObjectURL() in the blob backend.
+      const identity = ++sequence;
+      return `data:text/javascript;charset=utf-8,${encodeURIComponent(code)}#solid-tag-runtime-${identity}`;
     },
     revoke() {},
   };