@jsenv/core 41.3.0 → 41.3.1

package/dist/build/build.js

@@ -9158,6 +9158,16 @@ const jsenvPluginWorkspaceBundle = ({ packageDirectory }) => {
         // root package, we don't want to bundle
         return null;
       }
+      if (reference.type !== "js_import") {
+        // Only consolidate ES imports of a workspace package into its single
+        // bundle. Other reference kinds are their own entry points — most
+        // importantly an HTML <script src> pointing at a package file (jsenv
+        // injects its own client scripts that way: server events, the client
+        // monitoring reporter, custom-elements-redefine…). Redirecting those to
+        // the package main would run the wrong module, and for @jsenv/core the
+        // main is node-only code (node:url) that cannot be served to a browser.
+        return null;
+      }
       // we make sure we target the bundle version of the package
       // otherwise we might execute some parts of the package code multiple times.
       // so we need to redirect the potential reference to non entry point to the package main entry point

package/dist/start_dev_server/start_dev_server.js

@@ -6798,6 +6798,16 @@ const jsenvPluginWorkspaceBundle = ({ packageDirectory }) => {
         // root package, we don't want to bundle
         return null;
       }
+      if (reference.type !== "js_import") {
+        // Only consolidate ES imports of a workspace package into its single
+        // bundle. Other reference kinds are their own entry points — most
+        // importantly an HTML <script src> pointing at a package file (jsenv
+        // injects its own client scripts that way: server events, the client
+        // monitoring reporter, custom-elements-redefine…). Redirecting those to
+        // the package main would run the wrong module, and for @jsenv/core the
+        // main is node-only code (node:url) that cannot be served to a browser.
+        return null;
+      }
       // we make sure we target the bundle version of the package
       // otherwise we might execute some parts of the package code multiple times.
       // so we need to redirect the potential reference to non entry point to the package main entry point

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jsenv/core",
-  "version": "41.3.0",
+  "version": "41.3.1",
   "type": "module",
   "description": "Tool to develop, test and build js projects",
   "repository": {
@@ -78,7 +78,7 @@
     "@jsenv/plugin-minification": "1.7.5",
     "@jsenv/plugin-supervisor": "1.8.7",
     "@jsenv/plugin-transpilation": "1.5.78",
-    "@jsenv/server": "17.4.0",
+    "@jsenv/server": "17.4.1",
     "@jsenv/sourcemap": "1.4.2",
     "react-table": "7.8.0"
   },

package/src/plugins/workspace_bundle/jsenv_plugin_workspace_bundle.js

@@ -41,6 +41,16 @@ export const jsenvPluginWorkspaceBundle = ({ packageDirectory }) => {
         // root package, we don't want to bundle
         return null;
       }
+      if (reference.type !== "js_import") {
+        // Only consolidate ES imports of a workspace package into its single
+        // bundle. Other reference kinds are their own entry points — most
+        // importantly an HTML <script src> pointing at a package file (jsenv
+        // injects its own client scripts that way: server events, the client
+        // monitoring reporter, custom-elements-redefine…). Redirecting those to
+        // the package main would run the wrong module, and for @jsenv/core the
+        // main is node-only code (node:url) that cannot be served to a browser.
+        return null;
+      }
       // we make sure we target the bundle version of the package
       // otherwise we might execute some parts of the package code multiple times.
       // so we need to redirect the potential reference to non entry point to the package main entry point