Nix NodeJS - Public Room Timeline - Matrix Static

	Nix NodeJS	206 Members
		59 Servers

You have reached the beginning of time (for this room).

Sender	Message	Time
26 Mar 2025
hexa	ah, my bad 😄	20:57:18
27 Mar 2025
@rosssmyth:matrix.org	Hello. I have a pnpm+rsbuild package I am trying to build with nix. It used to build, but it does not any longer. I'm unsure in the exact change that has caused it, nor have my attempts at enabling logging actually enabled any useful logging. The error is: > rsbuild build > Rsbuild v1.2.19 > > 🧐 Checking for wasm-pack... > > ✅ wasm-pack is installed at /build/source/node_modules/.bin/wasm-pack. > > ℹ️ Compiling your crate in release mode... > > Error fetching release: getaddrinfo EAI_AGAIN github.com > 🧐 Checking for wasm-pack... > > ✅ wasm-pack is installed at /build/source/node_modules/.bin/wasm-pack. > > ℹ️ Compiling your crate in release mode... > > Error fetching release: getaddrinfo EAI_AGAIN github.com > 🧐 Checking for wasm-pack... > > ✅ wasm-pack is installed at /build/source/node_modules/.bin/wasm-pack. > > ℹ️ Compiling your crate in release mode... > > Error fetching release: getaddrinfo EAI_AGAIN github.com > ● web ━━━━━━━━━━━━━━━━━━━━━━━━━ (93%) sealing after asset optimization error Compile error: > Failed to compile, check the errors for troubleshooting. This is a TS project with some WASM. I poked around in the wasm pack plugin source and couldn't find where it may attempt to fetch some release. Outside of the sandbox it builds fine. Doing a bisect shows that three dependencies were added to the project in the commit that broke the sandboxed builds: `"devDependencies": { "vitest": "^2.1.8", "wasm-pack": "^0.13.1", "webpack-glsl-loader": "github:grieve/webpack-glsl-loader"`	21:25:06
@rosssmyth:matrix.org	* Hello. I have a pnpm+rsbuild package I am trying to build with nix. It used to build, but it does not any longer. I'm unsure in the exact change that has caused it, nor have my attempts at enabling logging actually enabled any useful logging. The error is: > rsbuild build > Rsbuild v1.2.19 > > 🧐 Checking for wasm-pack... > > ✅ wasm-pack is installed at /build/source/node_modules/.bin/wasm-pack. > > ℹ️ Compiling your crate in release mode... > > Error fetching release: getaddrinfo EAI_AGAIN github.com > 🧐 Checking for wasm-pack... > > ✅ wasm-pack is installed at /build/source/node_modules/.bin/wasm-pack. > > ℹ️ Compiling your crate in release mode... > > Error fetching release: getaddrinfo EAI_AGAIN github.com > 🧐 Checking for wasm-pack... > > ✅ wasm-pack is installed at /build/source/node_modules/.bin/wasm-pack. > > ℹ️ Compiling your crate in release mode... > > Error fetching release: getaddrinfo EAI_AGAIN github.com > ● web ━━━━━━━━━━━━━━━━━━━━━━━━━ (93%) sealing after asset optimization error Compile error: > Failed to compile, check the errors for troubleshooting. This is a TS project with some WASM. I poked around in the wasm pack plugin source and couldn't find where it may attempt to fetch some release. Outside of the sandbox it builds fine. Doing a bisect shows that three dependencies were added to the project in the commit that broke the sandboxed builds: `"devDependencies": { ... "vitest": "^2.1.8", "wasm-pack": "^0.13.1", "webpack-glsl-loader": "github:grieve/webpack-glsl-loader" }`	21:25:20
@rosssmyth:matrix.org	If anyone has any ideas as to what could be the issue or how to debug it further please let me know	21:25:34
@rosssmyth:matrix.org	My initial thought was something with github dependencies, but creating a dummy project with only the webpack-glsl-loader dependency works fine	21:26:20
@rosssmyth:matrix.org	Ok I removed the "wasm-pack" line in the package.json and it works	21:31:08
@rosssmyth:matrix.org	It does complain that it is not able to download wasm-opt, but it does compile	21:32:57
@rosssmyth:matrix.org	* It does complain that it is not able to download wasm-opt/binaryen, but it does compile	21:33:07
@rosssmyth:matrix.org	Yeah it seems to be some sort of issue when wasm-pack is in the dependency tree. Even if I put it in the optional dependencies then give it `--no-optional`, the build fails because something seems to expect it to exist	22:04:54
@rosssmyth:matrix.org	Upstream there are some issues open for this	22:05:12
28 Mar 2025
	beviu joined the room.	14:55:15
	tweqx joined the room.	15:03:57

Show newer messages

Back to Room ListRoom Version: 6