| 3 Dec 2025 |
 Tomodachi94 (they/them) | Yeah, ultimately the derivations have inputs that are platform-dependent like NodeJS and stdenv, which means different hashes for them | 19:23:55 |
 dish [Fox/It/She] | also buildNpmPackage prunes to packages for current platform only | 20:40:02 |
| dish [Fox/It/She] | and anything using node-gyp only gets built for host arch/os iirc | 20:40:27 |
| 5 Dec 2025 |
|  hsjobeki joined the room. | 18:10:06 |
| hsjobeki | (crossposting from the nixpkgs room)
Hi, @amopel built a dependency fetcher for Deno.
For those who don't know it: https://docs.deno.com/runtime/ (An evolution of node)
The PR is quite big, and I would be happy to find a person, who can help with the review process.
I tried to mentor the author in the PR already, but i think a second pair of eyes is required before we can merge it.
https://github.com/NixOS/nixpkgs/pull/453904 | 18:10:34 |
| dish [Fox/It/She] | wow, that is a very complex PR | 18:58:28 |
| dish [Fox/It/She] | which is my main concern with it, to be clear. There is both typescript and rust components, and the commits are not very well-organized(imo) | 19:07:16 |
| hsjobeki | He mentioned he would squash the commits afterwards | 19:14:41 |
| dish [Fox/It/She] | still though, the overall code complexity is high, no? | 19:15:41 |
| hsjobeki | Compexity is high, but also a good portion of the code are tests. | 19:16:01 |
| hsjobeki | Complexity is high, because deno doesnt have a repro-lockfile.
It is 'security' focused. With 3 different registry types supported. | 19:17:10 |
| hsjobeki | * Complexity is high, because deno doesnt have a repro-focused-lockfile.
It is 'security' focused. With 3 different registry types supported. | 19:18:28 |
| hsjobeki | The readme (1k lines) gives a good overview how deno locks its dependencies | 19:21:47 |
| hsjobeki | * The readme (900 lines) gives a good overview how deno locks its dependencies | 19:22:15 |
| 6 Dec 2025 |
| dish [Fox/It/She] | anyone opposed to me dropping every purescript-related package from nodePackages?(pscid, pulp, purescript-language-server, purescript-psa, and purs-tidy) | 18:34:12 |
| dish [Fox/It/She] | @Tomodachi94 (they/them) | 18:34:14 |
| dish [Fox/It/She] | only reason to keep them is to build other purescript packages but that should rely on real tooling for purescript and not node2nix | 18:34:37 |
| dish [Fox/It/She] | * only reason to keep them is to build other purescript packages but that should rely on real tooling for purescript(doesn't currently exist tbf) and not node2nix | 18:35:52 |
| 7 Dec 2025 |
| dish [Fox/It/She] | gonna open a PR for this at least | 06:05:21 |
| Tomodachi94 (they/them) | I'm not particularly opposed to this. I took a stab at a PureScript build and couldn't get it to work | 20:52:19 |
| 8 Dec 2025 |
|  Gian joined the room. | 01:06:26 |
| 10 Dec 2025 |
|  @arexon:matrix.org left the room. | 12:22:15 |
| 13 Dec 2025 |
| dish [Fox/It/She] | submitted the PR, added you as a reviewer so it's on your radar ^^ | 03:28:29 |
|  NixOS Moderation Bot unbanned  @joepie91:pixie.town. | 05:59:00 |
| 14 Dec 2025 |
|  suua joined the room. | 13:32:48 |
| Tomodachi94 (they/them) | Filed an issue about the idmail stuff so that @oddlama knows about it: https://github.com/NixOS/nixpkgs/issues/470855 | 22:12:01 |
| Tomodachi94 (they/them) | For the remaining nodePackages, it might be better to ping the people who originally added them (if they're still around) to see if they can repackage them | 22:13:01 |
| dish [Fox/It/She] | many seem to come from like | 22:13:29 |
| dish [Fox/It/She] | wayyyyyyy back | 22:13:31 |
| dish [Fox/It/She] | lcov-results-merger was in the initial import to nodePackages | 22:13:45 |
