| 22 Dec 2022 |
Winter (she/her) | no. (why do you think it would?) | 14:50:54 |
aktaboot | still getting failed download, but now for another thing (esbuild-linux-64) | 14:51:01 |
aktaboot | In reply to @winterqt:nixos.dev no. (why do you think it would?) I assumed the error came from the fact that build process has no network access | 14:52:02 |
Winter (she/her) | In reply to @aktaboot:tchncs.de I assumed the error came from the fact that build process has no network access what setting that env var does is point it to what it wants from the network | 14:52:25 |
Winter (she/her) | so it doesn't try to download it | 14:52:30 |
Winter (she/her) | In reply to @aktaboot:tchncs.de still getting failed download, but now for another thing (esbuild-linux-64) huh, i don't think i ran into that. can you send the drv so i can repro and see what would be different, just for my tooling dev sake?
also: setting ESBUILD_BINARY_PATH = "${lib.getExe buildPackages.esbuild} should fix that. | 14:56:16 |
Winter (she/her) | sorry, drop the quote and the interpolation | 14:56:45 |
Winter (she/her) | just do = lib.getExe ... | 14:56:51 |
aktaboot | https://pastebin.com/x9YwNYGj | 14:57:25 |
Winter (she/her) | In reply to @aktaboot:tchncs.de still getting failed download, but now for another thing (esbuild-linux-64) * huh, i don't think i ran into that. can you send the drv so i can repro and see what would be different, just for my tooling dev sake?
also: setting ESBUILD_BINARY_PATH = lib.getExe buildPackages.esbuild should fix that. | 14:57:27 |
Winter (she/her) | In reply to @aktaboot:tchncs.de https://pastebin.com/x9YwNYGj i mean the source :) | 14:57:34 |
aktaboot | http://0x0.st/o5pQ.nix | 14:58:29 |
Winter (she/her) | In reply to @winterqt:nixos.dev huh, i don't think i ran into that. can you send the drv so i can repro and see what would be different, just for my tooling dev sake?
also: setting ESBUILD_BINARY_PATH = lib.getExe buildPackages.esbuild should fix that. aktaboot: did that fix end up working btw | 16:56:50 |
aktaboot | Winter (she/her) no, It is pulling a different version of esbuild
error /build/source/node_modules/esbuild: Command failed.
Exit code: 1
Command: node install.js
Arguments:
Directory: /build/source/node_modules/esbuild
Output:
/build/source/node_modules/esbuild/install.js:81
throw new Error(`Expected ${JSON.stringify(version)} but got ${JSON.stringify(stdout)}`);
^
Error: Expected "0.9.7" but got "0.16.7"
at validateBinaryVersion (/build/source/node_modules/esbuild/install.js:81:11)
at installDirectly (/build/source/node_modules/esbuild/install.js:191:5)
at installOnUnix (/build/source/node_modules/esbuild/install.js:221:5)
at Object.<anonymous> (/build/source/node_modules/esbuild/install.js:248:3)
at Module._compile (node:internal/modules/cjs/loader:1159:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
at Module.load (node:internal/modules/cjs/loader:1037:32)
at Module._load (node:internal/modules/cjs/loader:878:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:23:47
| 17:25:14 |
aktaboot | not sure if the different version is the cause of the error or not | 17:25:28 |
Winter (she/her) | In reply to @aktaboot:tchncs.de
Winter (she/her) no, It is pulling a different version of esbuild
error /build/source/node_modules/esbuild: Command failed.
Exit code: 1
Command: node install.js
Arguments:
Directory: /build/source/node_modules/esbuild
Output:
/build/source/node_modules/esbuild/install.js:81
throw new Error(`Expected ${JSON.stringify(version)} but got ${JSON.stringify(stdout)}`);
^
Error: Expected "0.9.7" but got "0.16.7"
at validateBinaryVersion (/build/source/node_modules/esbuild/install.js:81:11)
at installDirectly (/build/source/node_modules/esbuild/install.js:191:5)
at installOnUnix (/build/source/node_modules/esbuild/install.js:221:5)
at Object.<anonymous> (/build/source/node_modules/esbuild/install.js:248:3)
at Module._compile (node:internal/modules/cjs/loader:1159:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
at Module.load (node:internal/modules/cjs/loader:1037:32)
at Module._load (node:internal/modules/cjs/loader:878:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:23:47
you'll need to pull that version then | 17:25:35 |
Winter (she/her) | and use that instead | 17:25:40 |
aktaboot | I am not sure how to do that with nix | 17:28:15 |
Winter (she/her) | In reply to @aktaboot:tchncs.de I am not sure how to do that with nix you can do this: https://github.com/NixOS/nixpkgs/blob/04f574a1c0fde90b51bf68198e2297ca4e7cccf4/pkgs/applications/networking/instant-messengers/deltachat-desktop/default.nix#L37 | 17:29:30 |
aktaboot | moved some more general nix-question to main room | 18:18:08 |
| 25 Dec 2022 |
| @ahsmha:matrix.org left the room. | 10:36:37 |
| 6 Jan 2023 |
| Linus joined the room. | 00:56:31 |
| Lily Foster joined the room. | 01:14:07 |
| zebrag joined the room. | 01:24:04 |
| 7 Jan 2023 |
| aktaboot changed their profile picture. | 20:27:20 |
| 9 Jan 2023 |
| @adis:blad.is left the room. | 06:27:07 |
| 12 Jan 2023 |
| stroem - sourcegraph joined the room. | 20:43:46 |
stroem - sourcegraph | How do I set the nodejs used by a package in nixpkgs.nodePackages? Ive tried .override { nodejs = pkgs.nodejs_16-x; } but thats not doing the job | 20:55:28 |
stroem - sourcegraph | nodejs-16_x.pkgs.pnpm doesnt add pnpm to path like nodePackages.pnpm does | 21:01:34 |
stroem - sourcegraph | ive also tried an overlay to set global nodejs = nodejs-16_x; to no avail, as well as the approach from here https://discourse.nixos.org/t/how-to-use-pnpm-with-recent-nodejs/21867/2, which adds nodejs16 to the PATH of /nix/store/s01asphglgvimr64ymbddc0lf8ln7rs1-pnpm-7.24.2/bin/pnpm, but that script invokes /nix/store/s01asphglgvimr64ymbddc0lf8ln7rs1-pnpm-7.24.2/bin/.pnpm-wrapped which has node 14 in its shebang | 21:12:19 |