| 28 May 2023 |
 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 |
| Lily Foster | (If so, the answer is no because it's all cache FODs from the lockfiles. If there was something like importCargoLock then those would be I suppose by nature of how Nix works but until computed derivations you don't want to use that in nixpkgs mostly) | 15:04:50 |
| Lily Foster | In reply to @hellwolf:matrix.org
Like not having the same thing in the nix store twice Yeah no, given it generates npm caches for all deps as a single FOD. The amount of dedup that would do is probably not as much as you're expecting but one day it'll be able to do that | 15:05:51 |
| hellwolf | do you think auto-optimise-store = true will do some extra magic still? | 15:07:12 |
| Lily Foster | Good question. Probably? I forget how exactly that determines what to hard link but I suppose it will | 15:08:09 |
| Lily Foster | Due to the way npm's cacache works | 15:08:27 |
|  @yuu:matrix.org left the room. | 20:31:26 |
| 30 May 2023 |
|  Emma [it/its] joined the room. | 12:07:30 |
