In reply to @lily:lily.flowers
(ugh npm makes me sad)

In reply to @janne.hess:helsinki-systems.de
try yarn, might make you sadder

In reply to @lily:lily.flowers
i doubt that tbh. sure it's missing some stuff we want for reproducibility, but at least it felt somewhat more intelligently designed

➤ 8;;https://yarnpkg.com/advanced/error-codes#yn0060---incompatible_peer_dependencyYN00608;;: │ vitest@npm:0.34.6 [f9b2d] provides @types/node (pe6001) with version 16.9.1, which doesn't satisfy what vite requests

In reply to @janne.hess:helsinki-systems.de

➤ 8;;https://yarnpkg.com/advanced/error-codes#yn0060---incompatible_peer_dependencyYN00608;;: │ vitest@npm:0.34.6 [f9b2d] provides @types/node (pe6001) with version 16.9.1, which doesn't satisfy what vite requests

In reply to @lily:lily.flowers
(now if only their lockfile format was sane....)

In reply to @janne.hess:helsinki-systems.de
it is with berry

/nix/store/q1c2flcykgr4wwg5a6h450hxbk4ch589-bash-5.2-p15/bin/sh: line 1: c++filt: command not found
/nix/store/q1c2flcykgr4wwg5a6h450hxbk4ch589-bash-5.2-p15/bin/sh: line 1: readelf: command not found

I will leave this here for future reference:

  yarnFailHook = /* bash */ ''
    printYarnErrors() {
      cat /build/xfs-*/build.log
    }
    failureHooks+=(printYarnErrors)
  '';

-in stdenvNoCC.mkDerivation {
+in stdenv.mkDerivation {
   pname = "cal.com";
   inherit version;

   inherit src;

-  nativeBuildInputs = [ yarn-berry makeBinaryWrapper ];
+  nativeBuildInputs = [ yarn-berry makeBinaryWrapper pkg-config python3 ];
+  buildInputs = [ vips ];
+
+  npm_config_node_gyp = "${nodejs_18}/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js";
+  npm_config_nodedir = srcOnly nodejs_18;

   patches = [
     (fetchpatch {

this is what it took to fix it. thank you so much Lily Foster 🥳

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