| 28 May 2023 |
 Lily Foster | buildNpmPackage is really more for leaf-like application-level npm packages | 14:12:03 |
| Lily Foster | At some point we may end up trying to build out a real Nix-based node package set, but npm dependencies go really deep. Unlike how other package sets like python generally are | 14:14:08 |
| Lily Foster | So I doubt it'll really be worth it tbh | 14:14:23 |
| Lily Foster | We'll probably aim for more like how the rust stuff works | 14:14:35 |
| Lily Foster | I want to have something like importCargoLock but for package-lock.json but it's far down on the backburner rn | 14:15:12 |
 hellwolf |
npm dependencies go really deep.
Indeed. I wonder if it's inherit to node, or just how npm/yarn works.
| 14:21:15 |
| Lily Foster | In reply to @hellwolf:matrix.org
npm dependencies go really deep.
Indeed. I wonder if it's inherit to node, or just how npm/yarn works.
Tbh just how any similar system works. See Mix/Elixir, Rust/Cargo, Go, etc. Those don't go as deep as npm but they do get large | 14:23:00 |
| hellwolf | I see. | 14:45:41 |
| hellwolf | One more question, when using buildNpmPackage packages. do packages still share the build outputs of their dependencies if possible? | 14:46:12 |
| Lily Foster | In reply to @hellwolf:matrix.org
One more question, when using buildNpmPackage packages. do packages still share the build outputs of their dependencies if possible? How do you mean exactly? | 15:01:56 |
| Lily Foster | Like sharing dependency sources? | 15:02:07 |
| hellwolf | Like not having the same thing in the nix store twic | 15:04:32 |
| hellwolf | * Like not having the same thing in the nix store twice | 15:04:33 |
