| 29 Apr 2025 |
 Cathal | Yeah I see what you mean now. I wonder if the yarnInstallHook has any support for PNP mode? Probably not though. | 16:38:45 |
 c3n21 | Yeah, at this point I'm wondering if I should just wait the release of 7.x as the author told me that it will use pnpm or just try to hack this around | 16:44:21 |
| Cathal | I'm no yarn expert, but from a quick search seems that it should be possible to wrap the end binary to correctly pass the .pnp files, or set an env var. I came across this for example: https://github.com/madjam002/yarnpnp2nix/blob/master/lib/mkYarnPackage.nix#L196-L197 | 16:48:16 |
| Cathal | Might be more trouble than it's worth for the Verdaccio pakcage specifically, since they're switching to pnpm anyways, but there will likely be other packages who hit this issue in the future. | 16:51:29 |
| Cathal | * Might be more trouble than it's worth for the Verdaccio package specifically, since they're switching to pnpm anyways, but there will likely be other packages who hit this issue in the future. | 16:51:36 |
| c3n21 | Yes this did indeed work, the only problem is that I'm not so acquaintanted with Nix packaging and I don't know if a node package can also have a wrapper | 16:57:25 |
| c3n21 | Yes I think that perhaps it should be wiser to package it for pnpm for now and use the unstable versioning till 7.x is released.
Meanwhile I will raise the topic about pnp
| 16:58:55 |
| Cathal | Wrapping node packages is fine, here's an example of the Prisma package doing it: https://github.com/NixOS/nixpkgs/blob/master/pkgs/by-name/pr/prisma/package.nix#L83-L87 | 17:00:52 |
|  DolceTriade joined the room. | 23:12:13 |
| DolceTriade | Hello, I've been searching for a way to override the version of nodejs when using buildNpmPackage, but when I do this using the ways I know of, it always also includes the original version of the nodejs in the closure. For example, I'm trying to build mongosh with a newer version of nodejs, so I'm doing something like buildNpmPackage { ... nodejs = nodejs_23; };. Is there a way to ensure the original version of nodejs is not included? | 23:17:59 |
| DolceTriade | I've also tried buildNpmPackage.override { nodejs = nodejs_23; }. And also tried to use a nixpkgs overlay to override nodejs = nodejs_23 | 23:19:15 |
| DolceTriade | Redacted or Malformed Event | 23:19:21 |
| DolceTriade | Actually I think the overlay method works. I just had to overlay buildPackages instead of pkgs... Now to figure out how to remove nodejs-source from the closure | 23:25:46 |
| 9 May 2025 |
|  @gdesforges:matrix.org left the room. | 17:07:02 |
| 14 May 2025 |
 Winter | i'm not sure what you mean by this -- (buildNpmPackage.override { nodejs = ...; }) { ... } should work just fine | 00:22:34 |
| Winter | i'm not sure what you mean by the buildPackages part -- (buildNpmPackage.override { nodejs = ...; }) { ... } should work just fine | 00:22:44 |
| DolceTriade | Dunno...
buildPackages' = buildPackages.extend (self: super: {nodejs = nodejs_23;});
buildNpmPackage23 = buildNpmPackage.override {
buildPackages = buildPackages';
};
Ended up with something like this and this seemed to work. There are probably better ways to do this 🤷
| 22:37:02 |
| DolceTriade | I think I traced this down to npm-hooks or something | 22:37:19 |
| DolceTriade | We don't properly passthrough nodejs down there | 22:37:30 |
| 17 May 2025 |
|  terrorjack set a profile picture. | 08:53:40 |
| 21 May 2025 |
|  ofalvai joined the room. | 14:05:08 |
| 24 May 2025 |
|  @sfkvso:matrix.org left the room. | 18:59:50 |
| 2 Jun 2025 |
|  matrixrooms.info mod bot (does NOT read/send messages and/or invites; used for checking reported rooms) joined the room. | 18:19:07 |
| 7 Jun 2025 |
| matrixrooms.info mod bot (does NOT read/send messages and/or invites; used for checking reported rooms) left the room. | 22:26:01 |
| matrixrooms.info mod bot (does NOT read/send messages and/or invites; used for checking reported rooms) joined the room. | 23:42:43 |
| 9 Jun 2025 |
|  SigmaSquadron joined the room. | 13:17:03 |
| 22 Jun 2025 |
|  SomeoneSerge (Ever OOMed by Element) changed their display name from SomeoneSerge (UTC+U[-12,12]) to SomeoneSerge (Ever OOMed by Element). | 12:13:53 |
| 23 Jun 2025 |
 rosssmyth | For a package I maintain it requires a binary to be in a specific part of its project directory. Previously I copied it into the directory. I am trying to instead symlink it so that there isn't a duplicate binary around. But it seems that however npm decides what parts of the project directory are put in "node_modules/@project/...", the symlink is not preserved. I've tried passing npmFlags = [ "--preserve-symlinks" ]; but that did not seem to change anything. | 22:31:48 |
| rosssmyth | Anyone know what's going on? | 22:31:55 |
| 25 Jun 2025 |
|  @neobrain:matrix.org joined the room. | 14:13:17 |
