@gjsify/resolve-npm 0.4.32 → 0.4.33

package/lib/index.mjs

@@ -279,15 +279,33 @@ export const ALIASES_WEB_FOR_NODE = {
     // Bare specifiers → native re-exports (works for both named and side-effect imports)
     'abort-controller': '@gjsify/abort-controller/globals',
     'compression-streams': '@gjsify/compression-streams/globals',
-    'dom-events': '@gjsify/dom-events/globals',
+    // dom-events deliberately routes to the polyfill on Node — globals.mjs
+    // is browser-targeted (re-exports the full lib.dom event class hierarchy
+    // from globalThis), but Node 22 only ships Event/EventTarget/CustomEvent
+    // natively (no UIEvent / MouseEvent / KeyboardEvent / WheelEvent /
+    // PointerEvent / InputEvent / FocusEvent / …). Routing the bare specifier
+    // to the polyfill keeps the full class hierarchy available on Node; the
+    // polyfill subclasses native Event/EventTarget where present and supplies
+    // the rest. The `/globals` path remains reachable for browser builds via
+    // the dynamic per-runtimes-triplet resolver in `runtime-aliases.mjs`.
+    'dom-events': '@gjsify/dom-events',
     'dom-exception': '@gjsify/dom-exception/globals',
     'message-channel': '@gjsify/message-channel/globals',
-    'eventsource': '@gjsify/eventsource/globals',
-    // 'fetch' bare specifier is intentionally not aliased on Node:
-    // fetch/Headers/Request/Response/FormData are native globals since Node 18,
-    // so specs / app code should read them off globalThis. Users who need the
-    // value form should `import { fetch } from '@gjsify/fetch'` explicitly.
-    // 'fetch': '@gjsify/fetch/globals',
+    // eventsource deliberately routes to the polyfill on Node — globals.mjs
+    // re-exports `globalThis.EventSource`, but Node 24.x doesn't ship native
+    // EventSource at all (added experimentally in 22.3, requires the
+    // --experimental-eventsource flag on many distributions). The polyfill
+    // itself uses `fetch` + ReadableStream — both native on Node 18+ — and
+    // works without any GJS deps; routing to it gives consumers a working
+    // EventSource on Node out of the box. Same fix pattern as the `dom-events`
+    // entry above.
+    'eventsource': '@gjsify/eventsource',
+    // 'fetch' routes to @gjsify/fetch/globals on Node — the globals.mjs
+    // re-exports the native globalThis.{fetch,Request,Response,Headers,
+    // FormData} as named exports. The dynamic resolver routes
+    // @gjsify/fetch to the same /globals subpath via its runtimes
+    // triplet declaration (`node:"native"`), so both entry forms converge.
+    'fetch': '@gjsify/fetch/globals',
     'formdata': '@gjsify/formdata/globals',
     'html-image-element': '@gjsify/html-image-element',
     'webcrypto': '@gjsify/webcrypto/globals',

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@gjsify/resolve-npm",
-    "version": "0.4.32",
+    "version": "0.4.33",
     "description": "Resolve NPM package aliases",
     "type": "module",
     "main": "lib/index.mjs",