!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

193 Members
57 Servers

Load older messages

SenderMessageTime
6 Mar 2025
@joaomoreira:matrix.orgJoão Moreira * Guix people totally discard FODs on their official repos. I'm not sure if non-guix people embraced FODs.04:30:55
@joaomoreira:matrix.orgJoão Moreira * Guix totally discards FODs on their official repos. I'm not sure if non-guix people embraced FODs.04:31:14
@joaomoreira:matrix.orgJoão Moreira * Guix totally discards FODs on their official repos. I'm not sure if nonguix people embraced FODs.04:32:00
@magic_rb:matrix.redalder.orgmagic_rb
In reply to @joaomoreira:matrix.org
many/all modern ecosystems in Nixpkgs are only really feasible with FODs. Until someone proves the contrary. I also dislike it, but that's what we have.
Oh i know and agree. But still make me sad :( 		05:33:49
7 Mar 2025
@qyriad:katesiria.orgQyriad changed their display name from Qyriad to qyriad.16:44:27
8 Mar 2025
@qyriad:katesiria.orgQyriad changed their display name from qyriad to Qyriad.21:41:03
11 Mar 2025
@avocadoom:avocadoom.deavocadoom changed their profile picture.16:36:23
20 Mar 2025
@ahbk:matrix.orgI use NixOS btw set a profile picture.08:17:25
@ahbk:matrix.orgI use NixOS btw changed their profile picture.08:17:57
@ahbk:matrix.orgI use NixOS btw changed their display name from ahbk to I use NixOS btw.16:16:22
25 Mar 2025
@marie:marie.cologneMarie changed their display name from Marie to Marie Ramlow.17:42:27
@marie:marie.cologneMarie changed their display name from Marie Ramlow to Marie.17:44:54
26 Mar 2025
@hexa:lossy.networkhexado we have a prefetcher for pnpm?20:43:36
@hexa:lossy.networkhexa asking for one out of date discourse, which we run on discourse.nixos.org 20:45:34
@hexa:lossy.networkhexahm, enoscrumplex20:48:13
@hexa:lossy.networkhexa 
nix-repl> :b pnpm_9.fetchDeps { pname = "discourse"; src = /tmp/discourse; hash = ""; }
warning: found empty hash, assuming 'sha256-AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA='
error: build of '/nix/store/i96hrd6k8k1d1kjccpkp9sqfdm1xwvlr-discourse-pnpm-deps.drv' on 'ssh://hexa@build1.darmstadt.ccc.de' failed: builder for '/nix/store/i96hrd6k8k1d1kjccpkp9sqfdm1xwvlr-discourse-pnpm-deps.drv' failed with exit code 1;
       last 8 log lines:
       > Running phase: unpackPhase
       > unpacking source archive /nix/store/9vkknlvpk9k2r13k1pa7xxfbnr8a7xrm-discourse
       > source root is discourse
       > Running phase: patchPhase
       > Running phase: updateAutotoolsGnuConfigScriptsPhase
       > Running phase: installPhase
       > yq: Error running jq: ScannerError: mapping values are not allowed in this context
       >   in "pnpm-lock.yaml", line 209, column 75.
       For full logs, run 'nix log /nix/store/i96hrd6k8k1d1kjccpkp9sqfdm1xwvlr-discourse-pnpm-deps.drv'.
20:56:43
@hexa:lossy.networkhexaah, my bad 😄 20:57:18
27 Mar 2025
@rosssmyth:matrix.org@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@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@rosssmyth:matrix.orgIf anyone has any ideas as to what could be the issue or how to debug it further please let me know21:25:34
@rosssmyth:matrix.org@rosssmyth:matrix.orgMy initial thought was something with github dependencies, but creating a dummy project with only the webpack-glsl-loader dependency works fine21:26:20
@rosssmyth:matrix.org@rosssmyth:matrix.orgOk I removed the "wasm-pack" line in the package.json and it works21:31:08
@rosssmyth:matrix.org@rosssmyth:matrix.orgIt does complain that it is not able to download wasm-opt, but it does compile21:32:57
@rosssmyth:matrix.org@rosssmyth:matrix.org* It does complain that it is not able to download wasm-opt/binaryen, but it does compile21:33:07
@rosssmyth:matrix.org@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@rosssmyth:matrix.orgUpstream there are some issues open for this22:05:12
28 Mar 2025
@beviu:matrix.orgbeviu joined the room.14:55:15
@tweqx:matrix.orgtweqx joined the room.15:03:57
@beviu:matrix.orgbeviu Hi, we would like to package Overleaf based on work from an existing draft PR at https://github.com/NixOS/nixpkgs/pull/216889. One problem with Overleaf is that it has Git dependencies in its package.json file that have build scripts but do not have a package-lock.json file, and fetch-npm-deps doesn't support that (and rightly so, because it would not be reproducible). In that PR, the authors created a Python scripts that finds the Git dependencies in package.json, clones them, modifies the package.json to point to the clone, then run npm install to update the package-lock.json with the Git dependencies' transitive dependencies and commit that patched package-lock.json to Nixpkgs. We have a different idea where we would build the Git dependencies individually using buildNpmPackage, and then in the prePatch phase of Overleaf, we would modify the package-lock.json file in the prePatch phase to replace the Git dependencies with local dependencies that point to the output of the buildNpmPackage derivations. This would require modifying fetch-npm-deps to accept local dependencies (at least those that point to the Nix store in the form of "resolved": "/nix/store/..."). Do you think this would be the best approach? Would Nixpkgs accept a change to fetch-npm-deps to accept local dependencies? If so, maybe add a flag like --store-dir to fetch-npm-deps to tell it the location of the store (/nix/store) and only allow local dependencies under this directory? 15:12:13
@beviu:matrix.orgbeviu * Hi, we would like to package Overleaf based on work from an existing draft PR at https://github.com/NixOS/nixpkgs/pull/216889. One problem with Overleaf is that it has Git dependencies in its package.json file that have build scripts but do not have a package-lock.json file, and fetch-npm-deps doesn't support that (and rightly so, because it would not be reproducible). In that PR, the authors created a Python script that finds the Git dependencies in package.json, clones them, modifies the package.json to point to the clones, then runs npm install to update the package-lock.json with the Git dependencies' transitive dependencies and commit that patched package-lock.json to Nixpkgs. We have a different idea where we would build the Git dependencies individually using buildNpmPackage, and then in the prePatch phase of Overleaf, we would modify the package-lock.json file to replace the Git dependencies with local dependencies that point to the output of the buildNpmPackage derivations. This would require modifying fetch-npm-deps to accept local dependencies (at least those that point to the Nix store in the form of "resolved": "/nix/store/..."). Do you think this would be the best approach? Would Nixpkgs accept a change to fetch-npm-deps to accept local dependencies? If so, maybe add a flag like --store-dir to fetch-npm-deps to tell it the location of the store (/nix/store) and only allow local dependencies under this directory? 15:13:55

Show newer messages

Back to Room ListRoom Version: 6