bump elm node packages

[domenkozar]

Description of changes

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[turboMaCk]

2 packages marked as broken and skipped:
elmPackages.elm-coverage elmPackages.elm-verify-examples

2 packages failed to build:
elmPackages.elm-land elmPackages.elm-pages

The marked as broken are not a new thing and were discussed in some past PR.

The failure in elm-land and elm-pages might be a blocker though. cc @zupo @jali-clarke

[domenkozar]

Yeah those should work - any idea why linux packages were removed?

[turboMaCk]

I did not try to investigate it but my first guess from:

       > npm ERR! [esbuild] Trying to download "https://registry.npmjs.org/@esbuild/linux-x64/-/linux-x64-0.20.2.tgz"
       > npm ERR! [esbuild] Failed to download "https://registry.npmjs.org/@esbuild/linux-x64/-/linux-x64-0.20.2.tgz": getaddrinfo EAI_AGAIN registry.npmjs.org

is that npm install (or post-install or so) tries to download the tgz from the internet which fails in the sandbox. I'm not sure why it needs to download it or what initiates that download. Maybe it could avoided. If not I think we can try to fetch this using nix and put them into the node_modules in patchPhase which might be enough for npm to skip trying to fetch these cowboy-style. Likely these are invisible to node2nix since npm allows any sort of user defined effect in the install phase.

[domenkozar]

We should try again