Hi, two things. First thing I am hoping to learn to package JS/TS programs, I am fairly early in my nix journey but have read through the nix pills and had a look through the manuals but I am finding the interop with npm lock files a bit of a blocker to my understanding. It seems as if the prevailing solution is to use “generators” to create nix files from the lock files, but I am unsure as to whether that is just for ad hoc packaging or if the same approach is used within nixpkgs? Can anyone recommend a guide/section of the docs that cover this in an accessible way?

This leads me on to the second thing which is that https://github.com/microsoft/vscode-js-debug seems to be included somewhere to be available to VSCode but I don’t think it’s available standalone from nixpkgs, I would be interested in learning how to contribute it to nixpkgs, but that might require more help than creating a package request?

Heyo everyone,

I'd like to tell nixpkgs's buildNpmPackage which node version to use: nodejs_21 in my case.

How can I do it?

I could override the nodejs arguement but it also references buildPackages (which obviously is rather hard to override) and fetchNpmDeps.

https://github.com/NixOS/nixpkgs/blob/43eec8711993f851dc4f5dec16c0cb2fdb2b1d3a/pkgs/build-support/node/build-npm-package/default.nix#L4

In reply to @pkolloch:matrix.org

Heyo everyone,

I'd like to tell nixpkgs's buildNpmPackage which node version to use: nodejs_21 in my case.

How can I do it?

I could override the nodejs arguement but it also references buildPackages (which obviously is rather hard to override) and fetchNpmDeps.

https://github.com/NixOS/nixpkgs/blob/43eec8711993f851dc4f5dec16c0cb2fdb2b1d3a/pkgs/build-support/node/build-npm-package/default.nix#L4

In reply to @lily:lily.flowers
buildNpmPackage { ...; nodejs = nodejs_21; }

and the issue I get when building on x86_64-linux is

npm ERR! code 1
npm ERR! path /build/379k76sxq5hfcb5azx75c2k0y66q9p1i-source/node_modules/cypress
npm ERR! command failed
npm ERR! command sh -c node index.js --exec install
npm ERR! Installing Cypress (version: 12.7.0)
npm ERR!
npm ERR! [STARTED] Task without title.
npm ERR! The Cypress App could not be downloaded.
npm ERR!
npm ERR! Does your workplace require a proxy to be used to access the Internet? If so, you must configure the HTTP_PROXY environment variable before downloading Cypress. Read more: https://on.cypress.io/proxy-configuration
npm ERR!
npm ERR! Otherwise, please check network connectivity and try again:
npm ERR!
npm ERR! ----------
npm ERR!
npm ERR! URL: https://download.cypress.io/desktop/12.7.0?platform=linux&arch=x64
npm ERR! Error: getaddrinfo EAI_AGAIN download.cypress.io
npm ERR!
npm ERR! ----------
npm ERR!
npm ERR! Platform: linux-x64 (6.1.69)
npm ERR! Cypress Version: 12.7.0
npm ERR! [FAILED] The Cypress App could not be downloaded.
npm ERR! [FAILED]
npm ERR! [FAILED] Does your workplace require a proxy to be used to access the Internet? If so, you must configure the HTTP_PROXY environment variable before downloading Cypress. Read more: https://on.cypress.io/proxy-configuration
npm ERR! [FAILED]
npm ERR! [FAILED] Otherwise, please check network connectivity and try again:
npm ERR! [FAILED]
npm ERR! [FAILED] ----------
npm ERR! [FAILED]
npm ERR! [FAILED] URL: https://download.cypress.io/desktop/12.7.0?platform=linux&arch=x64
npm ERR! [FAILED] Error: getaddrinfo EAI_AGAIN download.cypress.io
npm ERR! [FAILED]
npm ERR! [FAILED] ----------
npm ERR! [FAILED]
npm ERR! [FAILED] Platform: linux-x64 (6.1.69)
npm ERR! [FAILED] Cypress Version: 12.7.0

npm ERR! Log files were not written due to an error writing to the directory: /nix/store/53jgj8pxhifcpqz5hf09j0i5jypngzll-remote-text-web-client-0.1.0-npm-deps/_logs
npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal

In reply to @julia:the-apothecary.club
I believe that darwin's nix config defaults to the sandbox being disabled, so that's probably why it builds there. (one could verify this assumption with --option sandbox true on macOS or --option sandbox false on Linux.

In reply to @julia:the-apothecary.club
From googling, it looks like there's a CYPRESS_RUN_BINARY and CYPRESS_INSTALL_BINARY variable which allows you to set it to an existing path. (https://docs.cypress.io/guides/references/advanced-installation)

In reply to @samasaur:matrix.org
so maybe set CYPRESS_INSTALL_BINARY=0 (to skip binary installs) and then set CYPRESS_RUN_BINARY=${pkgs.cypress}/bin/Cypress?

In reply to @samasaur:matrix.org
nix build . --sandbox still works on Darwin, so I think that's not it

actually, is this with a clean nix store / new build

because npmDepsHash implies to me the npm deps get put to the store separately; it's not gonna try redownload if it's specified already.
(not 100% on certain that's how it works, but I'd be surprised if it wasn't)

In reply to @samasaur:matrix.org
nix build . --sandbox still works on Darwin, so I think that's not it

actually, is this with a clean nix store / new build?

because npmDepsHash implies to me the npm deps get put to the store separately; it's not gonna try redownload if it's specified already.
(not 100% on certain that's how it works, but I'd be surprised if it wasn't)