| 13 Jan 2023 |
 Lily Foster | In reply to @strum355:matrix.org
22.11 pin seems to use 16.18.1, which i think is exactly what I need. Bit unfortunate I couldnt overwrite the nodejs version on the older pin though 🤔 I dont understand that exactly, has that issue been fixed since or is that still outstanding? You would have needed to also use the new node-env.nix though, which is why just overriding nodejs didn't do what you needed | 12:49:03 |
| Lily Foster | In reply to @strum355:matrix.org
22.11 pin seems to use 16.18.1, which i think is exactly what I need. Bit unfortunate I couldnt overwrite the nodejs version on the older pin though 🤔 I dont understand that exactly, has that issue been fixed since or is that still outstanding? You can do it with any nixpkgs pin after like mid-October, when all the dust settled on the nodePackages fixes | 12:49:38 |
 stroem - sourcegraph | nodejs always makes me sad, thanks for the help 🙂 | 12:52:11 |
| Lily Foster | In reply to @strum355:matrix.org
nodejs always makes me sad, thanks for the help 🙂 Same 🙃. Happy to help | 12:52:49 |
| Lily Foster | (To be clear, node2nix did not work with newer npm for a while so nodePackages was actually set to nodejs.pkgs.override { nodejs = nodejs-14_x; } to make it so that nodePackages didn't immediately break when nodejs was updated) | 12:54:07 |
| Lily Foster | (This was the PR to un-heck it: https://github.com/NixOS/nixpkgs/pull/193337) | 12:55:26 |
| 14 Jan 2023 |
|  Yuu Yin changed their display name from Yuu☯Yin to yuu. | 11:07:19 |
| 18 Jan 2023 |
| Yuu Yin changed their display name from yuu to Yuu Yin. | 13:42:43 |
| 31 Jan 2023 |
|  $nyx (it/its) joined the room. | 00:22:04 |
| 13 Feb 2023 |
| $nyx (it/its) changed their display name from Nyx (it/its) to $nyx (it/its). | 14:02:24 |
| 18 Feb 2023 |
 dotlambda | Is there a way to package a project using Yarn 3.3.1?
I'm trying to build https://github.com/home-assistant/frontend from source and hit https://github.com/NixOS/nixpkgs/issues/148042 on the way. | 16:56:12 |
 Winter (she/her) | not atm unless you use node2nix | 16:58:56 |
| dotlambda | In reply to @winterqt:nixos.dev
not atm unless you use node2nix But that would only read package.json, not yarn.lock? | 16:59:48 |
| Winter (she/her) | you can nuke the yarn.lock and generate a lockfile from that | 17:00:52 |
| Winter (she/her) | *npm lockfile with npm install | 17:01:04 |
| Winter (she/her) | by that point you can just use fetchNpmDeps
though that lockfile size may be huge ugh | 17:01:25 |
| dotlambda | Has anyone tried using https://github.com/imsnif/synp ? I wonder if it's deterministic | 17:01:25 |
| dotlambda | Oh, same issue though: https://github.com/imsnif/synp/issues/95 | 17:02:03 |
| Winter (she/her) | it requires an already populated node_modules tree :/ | 17:02:13 |
| Winter (she/her) | and probably doesn't support v3 | 17:02:20 |
| Winter (she/her) | * and probably doesn't support v2 | 17:02:23 |
| dotlambda | Well, no build from source then. | 17:03:58 |
| Lily Foster | In reply to @winterqt:nixos.dev
not atm unless you use node2nix We have the yarn fetcher, so they can use that, right? | 17:07:20 |
| Winter (she/her) | not with v2 | 17:08:42 |
| Lily Foster | v2 what? | 17:09:10 |
| Winter (she/her) | yarn | 17:09:28 |
| Winter (she/her) | entirely different lockfile format | 17:09:33 |
| Lily Foster | Ohhh right forgot about that | 17:09:45 |
| dotlambda | In reply to @lily:lily.flowers
v2 what? https://github.com/yarnpkg/berry | 17:09:51 |
| Lily Foster | In reply to @robert:funklause.de
https://github.com/yarnpkg/berry Yeah I knew about it but have mostly tried to ignore its existence. We don't have tooling for it so something like node2nix (that locks in Nix code rather than yarn.lock) might be one of the only solutions | 17:11:05 |
