| 21 May 2023 |
 raitobezarius | yes :D | 15:27:00 |
 Lily Foster | In reply to @raitobezarius:matrix.org
I have been dreaming those last days about starting the yarn backend for buildNpmPackage I've a few open yarn PRs to help that and there's a draft buildYarnPackage too we'll pick up soon | 15:27:05 |
 hexa | and https://github.com/NixOS/nixpkgs/pull/230991? 😲 | 19:50:04 |
| hexa | should we merge botamusique and navidrome with the npmCOnfigHook reschedule hack? | 19:50:34 |
| hexa | * should we merge botamusique and navidrome with the npmConfigHook reschedule hack? | 19:50:39 |
| Lily Foster | In reply to @hexa:lossy.network
should we merge botamusique and navidrome with the npmConfigHook reschedule hack? Given it unblocks those packages, I was starting to think we should just go ahead and merge the npmRoot PR and do further review items in follow-up PRs (and backport post branchoff) | 20:43:35 |
| Lily Foster | I would like npmRoot, I was just still wondering if we wanted it on the other hooks so that it worked with buildNpmPackage and wondering if we wanted it also on fetchNpmDeps. But that doesn't need to be a blocker | 20:44:37 |
| hexa | Did the npmRoot change work for botamusique? Because it caused problems with navidrome. | 20:44:41 |
| Lily Foster | In reply to @hexa:lossy.network
Did the npmRoot change work for botamusique? Because it caused problems with navidrome. Oh really? I hadn't tested yet | 20:44:55 |
