| 9 May 2023 |
 Lily Foster | It does not add it to the store by default | 10:56:12 |
| Lily Foster | You'd have to actually use nix build for it to go to the store | 10:56:32 |
 denbrahe | Okay, I'll just loop nix-build then. Thanks! | 10:57:49 |
| Lily Foster | Try --cores 1 on your nix-build command if you haven't already, since that might help | 10:58:45 |
| Lily Foster | (Or maybe it's only --option cores 1 for the old cli... i forget) | 10:59:11 |
| denbrahe | I'll try both 😛 | 11:03:40 |
| denbrahe | 100 retries, got nothing. Is this normal? It's a small project, only notable deps are react and typescript | 11:32:01 |
| Lily Foster | Nope that's not normal. I'll see if I can get retry logic working today and will let you try it, if you can't get a successful build before then | 11:42:27 |
| Lily Foster | Also if it's ignoring nix's NUM_JOBS setting then I'll fix that too | 11:42:42 |
 aktaboot | In reply to @lily:lily.flowers
Yeah, I can do that in a bit opened an issue,
Do you know what needs to be done for that to work ? I am not sure where the parsing functions for yarnLock are defined, I guess we would add a yarnLock2 or yarnLockv2 for the newer version | 13:57:11 |
| Lily Foster | It uses upstream @yarnpkg/lockfile, but an older pre-berry version | 13:58:44 |
| aktaboot | berry is newer ? | 14:00:07 |
| Lily Foster | Yes. Yarn 2+ is berry | 14:02:52 |
| aktaboot | In reply to @lily:lily.flowers
Yes. Yarn 2+ is berry does that seems more like a package upstream issue ? | 14:04:32 |
| Lily Foster | It's not an upstream issue, we don't use the upstream parser yet. I haven't tried to see if that's the only requirement for fetchYarnDeps to work | 14:07:53 |
| Lily Foster | yarn2nix is hecked for berry though | 14:08:00 |
| aktaboot | (also I'm not trying to put pressure on you in any way :), I just wanted to open an issue for the record and other people to see eventually) | 14:08:23 |
| aktaboot | In reply to @lily:lily.flowers
yarn2nix is hecked for berry though oh, is there ongoing work on that ? 👀 | 14:09:11 |
| Lily Foster | In reply to @aktaboot:tchncs.de
oh, is there ongoing work on that ? 👀 yarn2nix makes me sad. So unless someone else is, no. We are creating buildYarnPackage, fetchYarnDeps, and stuff to just have shiny new stuff to use | 14:16:58 |
| Lily Foster | In reply to @aktaboot:tchncs.de
(also I'm not trying to put pressure on you in any way :), I just wanted to open an issue for the record and other people to see eventually) Yeah it's no pressure and I do need to make an issue (just been busy and currently busy at $dayjob) | 14:17:23 |
| Lily Foster | Oh I see you already made an issue. Thank you aktaboot ❤ | 14:24:23 |
| 10 May 2023 |
|  quentin joined the room. | 22:45:15 |
| quentin | What's the current state of packaging apps that use yarn v3 lockfiles? Is the only option yarn-plugin-nixify and committing the giant generated yarn-project.nix? | 22:48:14 |
| Lily Foster | In reply to @quentinmit:matrix.org
What's the current state of packaging apps that use yarn v3 lockfiles? Is the only option yarn-plugin-nixify and committing the giant generated yarn-project.nix? Pretty much just that. Or locking your own npm package-lock.json and using buildNpmPackage | 23:03:32 |
| Lily Foster | Unfortunately | 23:03:43 |
| quentin | In reply to @lily:lily.flowers
Unfortunately Are there issues I can follow for this? | 23:19:07 |
| Lily Foster | In reply to @quentinmit:matrix.org
Are there issues I can follow for this? https://github.com/NixOS/nixpkgs/issues/177762 is for yarn2nix but I'm probably going to hijack it for fetchYarnDeps/buildYarnPackage because yarn2nix makes me sad | 23:34:38 |
| quentin | Thanks, I had already found and subscribed to that one | 23:44:23 |
| 11 May 2023 |
|  justingrant left the room. | 00:30:53 |
| 12 May 2023 |
|  Federico Schonborn changed their profile picture. | 00:58:42 |
