nextjs strikes again...

remove image loader, won't work with API_ADDRESS at runtime...

for now, just use a custom image loader that does nothing to bypass next/image rules and avoid needing to change every single <Image /> component right now.

web/next.config.js

@@ -1,23 +1,12 @@
-/** @type {import('next').NextConfig} */
-
 const isStandalone = process.env.NEXT_BUILD_STANDALONE === "true";
 
-const API_ADDRESS =
-  process.env["NEXT_PUBLIC_API_ADDRESS"] ?? "http://localhost:8000";
-
-const apiURL = new URL(API_ADDRESS);
-
+/** @type {import('next').NextConfig} */
 const nextConfig = {
   output: isStandalone ? "standalone" : undefined,
   reactStrictMode: true,
   images: {
-    remotePatterns: [
-      {
-        protocol: apiURL.protocol.replace(":", ""),
-        hostname: apiURL.hostname,
-        port: apiURL.port,
-      },
-    ],
+    loader: "custom",
+    loaderFile: "./src/lib/asset/loader.js",
   },
 };
 

web/src/lib/asset/loader.js

@@ -0,0 +1,4 @@
+// don't even ask... TODO: remove next/image from everywhere.
+export default function myHackyWorkaround({ src }) {
+  return src;
+}