| 31 Oct 2024 |
 Lily Foster | legacy-peer-deps does the opposite of what i suggested | 20:48:44 |
| Lily Foster | by overeagerly including them | 20:48:55 |
 pxc | I thought it was the other way around
at any rate, removing it made no difference :( | 20:53:33 |
| pxc | * I thought it was the other way around. --legacy-peer-deps doesn't have any real documentation the npm install docs afaict, which is annoying
at any rate, removing it made no difference :(
| 20:54:55 |
| pxc | I'll try also adding --no-optional, I suppose | 20:55:32 |
| pxc | nope, esbuild is made about --no-optional. I guess if you use esbuild, optionalDependencies are actually required 🙃 | 20:58:07 |
| pxc | * nope, esbuild is mad about --no-optional. I guess if you use esbuild, optionalDependencies are actually required 🙃 | 20:58:14 |
| Lily Foster | In reply to @pxc:matrix.org
nope, esbuild is made about --no-optional. I guess if you use esbuild, optionalDependencies are actually required 🙃 you can trivially get around that but also the problem here isn't optionalDependencies, but optional peerDependencies which are different | 21:01:29 |
| Lily Foster | * you can trivially get around that (search elsewhere in nixpkgs for prior art on esbuild insanity) but also the problem here isn't optionalDependencies, but optional peerDependencies which are different | 21:02:25 |
| pxc | well I have low confidence in the correctness but I did get a build that ran! since you pointed me at the npmFlags related to peer dependencies, I skimmed the NodeJS docs and decided to try --omit peer in place of --legacy-peer-deps, and the build succeeded
the tool does run from that build and at least some commands work
| 21:15:29 |
| Lily Foster | i mean if it runs and there's no obvious issues it's probably fine | 21:18:15 |
| Lily Foster | i forget if there is a knob to more directly exclude only optional peer deps and am on mobile or i'd just check the tool/code | 21:18:55 |
| pxc | I'll switch to it on this machine (currently using the one from MacPorts) and test it for like a day then submit a PR | 21:19:03 |
| pxc | tyvvm for your help! | 21:23:00 |
| 1 Nov 2024 |
 @gdesforges:matrix.org | Is there a way to add a package to nodePackages without updating the entire set?
I'm following https://github.com/NixOS/nixpkgs/blob/master/doc/languages-frameworks/javascript.section.md#adding-and-updating-javascript-packages-in-nixpkgs-javascript-adding-or-updating-packages
But when I run ./pkgs/development/node-packages/generate.sh it starts a super long script that I guess updates pkgs/development/node-packages/node-packages.nix in its entirety.
Is there some incremental update that I'm unaware of?
Context: https://github.com/NixOS/nixpkgs/issues/351203 | 17:30:18 |
 Winter | use buildNpmPackage | 17:38:55 |
