sliftutils 1.7.35 → 1.7.37

package/index.d.ts

@@ -3353,6 +3353,10 @@ declare module "sliftutils/storage/remoteStorage/intermediateSources" {
 
 }
 
+declare module "sliftutils/storage/remoteStorage/productionEnv" {
+
+}
+
 declare module "sliftutils/storage/remoteStorage/remoteConfig" {
     /// <reference types="node" />
     /// <reference types="node" />
@@ -3553,6 +3557,7 @@ declare module "sliftutils/storage/remoteStorage/storageController" {
 }
 
 declare module "sliftutils/storage/remoteStorage/storageServer" {
+    import "./productionEnv";
     import "./accessPage";
     export type HostStorageServerConfig = {
         url: string;

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "sliftutils",
-    "version": "1.7.35",
+    "version": "1.7.37",
     "main": "index.js",
     "license": "MIT",
     "files": [

package/storage/remoteStorage/productionEnv.ts

@@ -0,0 +1,2 @@
+// Packages like mobx pick which build to require at runtime, from process.env.NODE_ENV. The browser require shim runs as production, so a server that loads the development build ships a module graph the client cannot satisfy ("Accessed unexpected module ./mobx.cjs.production.min.js ... Expected imports: ./mobx.cjs.development.js"). Setting this is the only way to make both sides agree, and it MUST happen before anything imports such a package - which is why it lives in its own module, imported first (import statements run in source order, so a plain statement at the top of storageServer.ts would run too late).
+process.env.NODE_ENV = "production";

package/storage/remoteStorage/storageServer.d.ts

@@ -1,3 +1,4 @@
+import "./productionEnv";
 import "./accessPage";
 export type HostStorageServerConfig = {
     url: string;

package/storage/remoteStorage/storageServer.ts

@@ -1,3 +1,5 @@
+// Must stay the FIRST import: it sets NODE_ENV, which decides which build of mobx (and anything else that switches on it) the imports below load
+import "./productionEnv";
 import os from "os";
 import path from "path";
 import fsp from "fs/promises";
@@ -89,8 +91,10 @@ export async function hostStorageServer(config: HostStorageServerConfig): Promis
     SocketFunction.expose(RequireController);
     SocketFunction.expose(RemoteStorageController);
     // Every HTTP path goes through httpEntry: /file/<account>/<bucketName>/... serves public bucket files, everything else serves the access page (the path is the account name, see accessPage.tsx). A full URL, so the page resolves modules from the origin root even when served at /accountName (a relative require would resolve inside the account path).
+    // The module path is resolved server-side against its working directory, which is the HOST application's folder - so it is computed from where this file actually is, instead of assuming the storage server runs from inside sliftutils (in a host app it lives under node_modules/sliftutils).
+    let accessPagePath = "./" + path.relative(process.cwd(), path.join(__dirname, "accessPage.tsx")).replaceAll("\\", "/");
     SocketFunction.setDefaultHTTPCall(RemoteStorageController, "httpEntry", {
-        requireCalls: [`https://${domain}:${port}/./storage/remoteStorage/accessPage.tsx`],
+        requireCalls: [`https://${domain}:${port}/${accessPagePath}`],
     });
 
     // Initial check so a server starting under-limit immediately rejects writes; then keep checking every 15 minutes so recovery (freed disk space) is picked up automatically.

package/storage/remoteStorage/storageServerCli.ts

@@ -1,4 +1,3 @@
-process.env.NODE_ENV = "production";
 import { hostStorageServer } from "./storageServer";
 import { getArg } from "./cliArgs";