@jsenv/core 41.5.35 → 41.5.38

package/dist/build/build.js

@@ -438,7 +438,7 @@ ${reason}`,
       return createFailedToFetchUrlContentError({
         code: "NOT_FOUND",
         reason: "no entry on filesystem",
-        ...detailsFromInjectionsOnOwner(urlInfo.firstReference),
+        ...detailsFromHtmlUrlNotFound(urlInfo.firstReference),
       });
     }
   }
@@ -698,6 +698,31 @@ const detailsFromInjectionsOnOwner = (reference) => {
   };
 };
 
+// An url of an html attribute leading to no file may be meant for a server rather
+// than for jsenv: a route of a backend, which "jsenv-ignore" leaves alone. Only the
+// build is concerned: in dev the browser requests the url whatever jsenv does with it.
+const detailsFromHtmlUrlNotFound = (reference) => {
+  const detailsFromInjections = detailsFromInjectionsOnOwner(reference);
+  if (detailsFromInjections.suggestion) {
+    return detailsFromInjections;
+  }
+  if (!reference) {
+    return {};
+  }
+  const ownerUrlInfo = reference.ownerUrlInfo;
+  if (ownerUrlInfo.type !== "html" || !ownerUrlInfo.context.build) {
+    return {};
+  }
+  const { node, attributeName } = reference.astInfo || {};
+  if (!node || !attributeName) {
+    return {};
+  }
+  return {
+    suggestion: `when "${reference.specifier}" is answered by a server rather than a file, add "jsenv-ignore" so the build leaves that url alone:
+<${node.nodeName} jsenv-ignore ${attributeName}="${reference.specifier}" />`,
+  };
+};
+
 const detailsFromPluginController = (jsenvPluginsController) => {
   const currentPlugin = jsenvPluginsController.getCurrentPlugin();
   if (!currentPlugin) {
@@ -9821,7 +9846,7 @@ const STATIC_IMPORT_SUBTYPES = ["import_static", "export_named", "export_all"];
  */
 
 
-const clientFileUrl = import.meta.resolve("../js/dependency_status.js");
+const clientFileUrl = import.meta.resolve("../client/dependency_status/dependency_status.js");
 
 const jsenvPluginDependencyStatus = ({
   dependencyProblemEventEmitter,