| 3 Sep 2025 |
 eyJhb | Running npm install --workspaces in the latest docker node container, I get these warnings.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @sidvind/better-ajv-errors@4.0.0
npm warn Found: ajv@8.17.1
npm warn node_modules/ajv
npm warn overridden ajv@"8.17.1" (was "^8.0.0") from ajv-formats@3.0.1
npm warn node_modules/ajv-formats
npm warn ajv-formats@"3.0.1" from appium@3.0.1
npm warn packages/appium
npm warn 1 more (appium)
npm warn
npm warn Could not resolve dependency:
npm warn peer overridden ajv@"8.17.1" (was "^7.0.0 || ^8.0.0") from @sidvind/better-ajv-errors@4.0.0
npm warn packages/appium/node_modules/@sidvind/better-ajv-errors
npm warn @sidvind/better-ajv-errors@"4.0.0" from appium@3.0.1
npm warn packages/appium
Might help some. God I hate npm/node
| 10:45:49 |
| eyJhb | nix-shell -p nodejs lerna
lerna clean
rm package-lock.json
npm install --workspaces --package-lock-only --ignore-scripts
This seems to work. Fucking hell. Might not have cleaned everything up? Maybe?
| 11:06:23 |
| eyJhb | ( Marie if you're curious ^ ) | 11:06:32 |
 Marie | nice you got it to work | 13:01:56 |
| Marie | it's insane how npm doesn't consider all of this a bug | 13:02:22 |
 n3tcat | npm is the bug :3 | 13:33:56 |
| eyJhb | I think it's very much a "works on my system". Like, we had to make a damn man in the middle proxy for Gradle last time I checked, because it's quite clearly insane :D | 15:19:50 |
| eyJhb | But thanks for rubber duckying me in PMs Marie, very much appreciated! I really want to get Appium upstreamed, so that other can use it, and most importantly, so I don't have to maintain it myself :p | 15:20:28 |
| n3tcat | 19:43:18 |
| n3tcat | 19:43:20 |
| n3tcat | 19:43:52 |
| n3tcat | 19:43:52 |
| n3tcat | 19:44:02 |
| 4 Sep 2025 |
|  @aidalgol:tchncs.de changed their display name from Aidan Gauland to aidalgol[m]. | 11:23:30 |
| @aidalgol:tchncs.de changed their display name from aidalgol[m] to aidalgol. | 11:24:12 |
| 5 Sep 2025 |
|  @ayatsfer:matrix.org left the room. | 11:23:00 |
| 6 Sep 2025 |
|  SomeoneSerge (back on matrix) changed their display name from SomeoneSerge (Ever OOMed by Element) to SomeoneSerge (@nixcon & back on matrix). | 09:24:34 |
| 7 Sep 2025 |
|  Ab Kein joined the room. | 04:51:50 |
| 9 Sep 2025 |
|  amaan set a profile picture. | 07:59:21 |
| amaan changed their profile picture. | 07:59:36 |
| amaan changed their profile picture. | 07:59:55 |
| 10 Sep 2025 |
| SomeoneSerge (back on matrix) changed their display name from SomeoneSerge (@nixcon & back on matrix) to SomeoneSerge (back on matrix). | 00:38:07 |
| 12 Sep 2025 |
| @aidalgol:tchncs.de set a profile picture. | 09:21:40 |
| 18 Sep 2025 |
|  mmkaram joined the room. | 08:33:21 |
| mmkaram | hello! I was trying to install the @prisma/language-server package from nixpkgs but it was marked as broken in March. It has since been fixed on npm, so I was thinking of trying to make a pr to add it back. The PR that removed it is here: https://github.com/NixOS/nixpkgs/commit/8af4a78d0d0486de96e0207eba72ff43382eb2dd
My question is all they changed was pkgs/development/node-packages/node-packages.json and pkgs/development/node-packages/main-programs.nix. There was no actual package.nix that was changed. To revert this change, would I just have to add the lines that were removed back? | 08:33:30 |
| mmkaram | I initially posted this in #dev:nixos.org but I was told that people here could help me with the details because nodePackages is supposed to be phased out or something | 08:34:19 |
| Marie | in theory yes, in practice no.
Ideally you would package it from source in a new package in pkgs/by-name/pr/prisma-language-server | 08:37:45 |
| mmkaram | I’m sure it can’t be that difficult I’ll try my hand at it today | 08:41:31 |
| mmkaram | Does anyone remember the name of the formatter for nix files? | 08:42:00 |
| Marie | nixfmt | 08:45:32 |
