| 25 Mar 2023 |
|  amardeeps joined the room. | 04:45:46 |
|  @valconius:matrix.org joined the room. | 23:45:57 |
| 26 Mar 2023 |
|  rbutani joined the room. | 00:26:14 |
| 31 Mar 2023 |
|  Ilan Joselevich (Kranzes) joined the room. | 00:53:32 |
| 5 Apr 2023 |
|  Redstone joined the room. | 05:48:00 |
|  @ulli:hrnz.li joined the room. | 18:41:17 |
| 6 Apr 2023 |
|  Lordie joined the room. | 14:01:06 |
| Lordie | Hi, I see that in the wiki there's an easy way to update the node packages in nixpkgs, by running ./pkgs/development/node-packages/generate.sh, however, running that script is not automated and I couldn't find a issue for it | 14:45:43 |
| Lordie | But I imagined that there's a reason for it not being automated yet | 14:45:50 |
| Lordie | I don't know if running that script would fit into this project | 14:46:20 |
 j-k | the script takes fooooreeeeeveeeeer to run.
I think nixpkgs-updates avoids any of the big language attributesets like JS & haskell AFAIK | 14:49:16 |
 hexa | it works for python packages, which is kinda big | 14:53:13 |
| hexa | but if you care about a package within nodePackages, and it uses packages-lock.json (aka npm), convert it to use buildNpmPackage and use nix-update as the updateScript | 14:53:56 |
| j-k | well for python most things are standalone right? like the package has it's own src. rather than a mega sources.json that gets mapped out to many packages? | 14:54:31 |
| hexa | yep | 14:55:33 |
| Lordie | In reply to @hexa:lossy.network
but if you care about a package within nodePackages, and it uses packages-lock.json (aka npm), convert it to use buildNpmPackage and use nix-update as the updateScript do you mean, pulling it out of nixpkgs/pkgs/development/node-packages into nixpkgs/pkgs/development/foo/bar and make a derivation using buildNpmPackage instead? | 15:02:01 |
| Lordie | In reply to @hexa:lossy.network
but if you care about a package within nodePackages, and it uses packages-lock.json (aka npm), convert it to use buildNpmPackage and use nix-update as the updateScript * do you mean, to pull it out of nixpkgs/pkgs/development/node-packages into nixpkgs/pkgs/development/foo/bar and make a derivation using buildNpmPackage instead? | 15:02:25 |
| hexa | yes | 15:02:42 |
| hexa | nodePackages is a disaster | 15:02:51 |
| Lordie | huh so for non-lib node packages, nixpkgs/pkgs/development/node-packages is sort a legacy way of doing things | 15:04:20 |
| Lordie | I'll make a PR, thanks | 15:04:59 |
| hexa | it made itself legacy due to the time required for generate.sh to run | 15:09:49 |
| hexa | also sometimes it just fails 2 hours in | 15:09:55 |
| hexa | the rough idea was to share package dependencies | 15:10:12 |
 Sandro š§ | node2nix does no parallelism | 15:38:25 |
| 12 Apr 2023 |
|  Yuddite G joined the room. | 09:11:02 |
| 16 Apr 2023 |
| Yuddite G changed their profile picture. | 23:09:30 |
| 20 Apr 2023 |
|  Federico DamiƔn Schonborn changed their display name from Federico DamiƔn Schonborn to Federico Schonborn. | 01:02:28 |
| 25 Apr 2023 |
|  @trofi:matrix.org left the room. | 15:45:11 |
| 26 Apr 2023 |
| Yuddite G changed their display name from Yuddite Pilot to Yuddite Groyper. | 04:49:01 |
