TL;DR;
I caused that blank screen mistake and have fixed it in v1.25.1.
Sorry my mistake, while moving to the new rust based message parser I needed to change the build script to run esbuild via it’s javascript api, instead of running it as it’s own process, while doing that I forgot to escape the value for process.env.NODE_ENV, so it was taking it as variable name and couldn’t find the variable production, because we never defined such a variable.
diff --git a/bin/build-frontend-ts.mjs b/bin/build-frontend-ts.mjs
index a4cfa6b8..ec7b0693 100755
--- a/bin/build-frontend-ts.mjs
+++ b/bin/build-frontend-ts.mjs
@@ -43,7 +43,7 @@ async function bundle(production, minify = false) {
sourcemap: true,
outfile: 'html-dist/bundle.js',
define: {
- 'process.env.NODE_ENV': production ? 'production' : 'development',
+ 'process.env.NODE_ENV': production ? '"production"' : '"development"',
},
plugins: [wasmPlugin],
})
So yes this was just one line that made the builds for 1.25.0 unusable.
We unfortunately didn’t test the final build ourselves this time, normally we test the builds before asking you to test them. I apologize sincerely for this inconvenience.