| 28 May 2023 |
 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 Yin left the room. | 20:31:26 |
| 30 May 2023 |
|  Emma [it/its] joined the room. | 12:07:30 |
|  @ulli:hrnz.li joined the room. | 12:08:58 |
| Emma [it/its] | i came here to ask, is there any progress on pnpm support? | 12:22:24 |
| Lily Foster | There won't be for a short while unless someone else is able to help work on it (it's somewhat far down the priority list) | 12:23:30 |
| Emma [it/its] | ah | 12:24:03 |
| 1 Jun 2023 |
 Pol | Anybody willing to help upgrading code-server ? It's throwing an error while building and I have no clue how to fix it . | 09:19:54 |
| Pol | The pr is here: https://github.com/NixOS/nixpkgs/pull/234289 | 09:21:23 |
| Pol | * Anybody willing to help upgrading code-server ? It's throwing an error while building and I have no clue how to fix it (I don't work with NodeJS). | 09:25:10 |
| Pol | * The pr is here: https://github.com/NixOS/nixpkgs/pull/234289, I also opened an issue upstream at: https://github.com/coder/code-server/issues/6244
Maybe this rings a bell to someone? | 09:25:56 |
|  raphi changed their display name from raphi to raphi (element unread channel fix when). | 13:03:14 |
 adamcstephens | Looks like you're blocked on nodejs18 and the upstream support? | 13:25:50 |
| 2 Jun 2023 |
| Pol | No, I must use NodeJS 16. There's no support of NodeJS 18 in coder/code-server yet. | 06:45:18 |
| Pol | I have another question for NodeJS maintainers, if any here. | 06:45:30 |
| Pol | I would like to review this PR (https://github.com/NixOS/nixpkgs/pull/235445) but I don't really know if the proposal is a good idea or not yet. | 06:45:59 |
| adamcstephens | In reply to @drupol:matrix.org
No, I must use NodeJS 16. There's no support of NodeJS 18 in coder/code-server yet. I understand that, but 16 was already marked as EOL for 23.05. | 13:22:54 |
| adamcstephens | Would we consider reverting that change for master/unstable until 16 actually becomes EOL in September? | 13:24:11 |
| Lily Foster | In reply to @drupol:matrix.org
No, I must use NodeJS 16. There's no support of NodeJS 18 in coder/code-server yet. I think that's what adamcstephens was saying | 13:35:17 |
| Lily Foster | In reply to @drupol:matrix.org
I would like to review this PR (https://github.com/NixOS/nixpkgs/pull/235445) but I don't really know if the proposal is a good idea or not yet. Request review from me and I'll get to it in the next day or two, thank you! | 13:35:36 |
| Lily Foster | In reply to @adam:valkor.net
Would we consider reverting that change for master/unstable until 16 actually becomes EOL in September? Release managers are not comfortable with that because 16 goes EOL 3.5 months before NixOS 23.05 does. We could maybe revert on master for now but idk if it's worth it for one package | 13:36:34 |
| Lily Foster | Oh I misread, that's what you were suggesting. Yeah maybe we could do that. I would want to know if more than one package is affected though | 13:37:35 |
| Lily Foster | (And still am a tad skeptical) | 13:37:48 |
 raitobezarius | We opened an issue on affected packages for Node.js 16 | 13:37:54 |
| raitobezarius | IMHO, it's not worth it, we should only press on and ping the maintainers so the ping their respective upstreams on going to Node.js 18 at least | 13:38:08 |
| raitobezarius | No matter what, we will find ourselves in September pretty quickly and given my experience with saying hi to upstream, they need time to accomodate | 13:38:27 |
