| 22 Nov 2023 |
 Lily Foster | In reply to @hexa:lossy.network
the reason I'm asking is mjolnir/draupnir, who both use yarn v1 lock files right now and are critical for the moderation team i agree they're at risk. my mental bandwidth has really been not great though, and no one has really stepped up about yarn-berry support :( | 23:27:47 |
 hexa | the worst case would be to stick them in a $DOCKER container and we'be okay | 23:28:34 |
| hexa | and don't worry about your personal bandwidth in that case | 23:28:50 |
| hexa | it is what it is | 23:28:52 |
| hexa | either some does it or not, but it is never any individuals fault | 23:28:59 |
| 23 Nov 2023 |
 @adis:blad.is | In reply to @lily:lily.flowers
idk i'd rather work on pnpm stuff at this point, but that's because the more i look into it, the more actually sane it looks (yaml lockfiles aside) What do you want to do with pnpm? I looked into it quite a bit a few years back. | 00:55:45 |
| @adis:blad.is | In reply to @whentze:matrix.org
so atm I have 2 questions adisbladis
- if I cleaned up the code to parse
.npmrc and pass auth headers based on it into fetchurl, would you be willing to take it?
- is
src != packageRoot supposed to work, or is it an unsupported configuration?
Is this something that would be possible to add to fetchurl or a custom fetcher? | 00:57:16 |
| @adis:blad.is | In reply to @whentze:matrix.org
the src/sourceRoot/npmRoot/packageRoot situation is quite confusing to me. no combination I've tried seems to work. Yeah.. Perhaphs I should rename packageRoot -> npmRoot | 00:57:44 |
| @adis:blad.is | They're the same thing | 00:57:47 |
| @adis:blad.is | It just felt more symmetric with package/packageJson/packageRoot | 00:58:09 |
| @adis:blad.is | In reply to @hexa:lossy.network
the reason I'm asking is mjolnir/draupnir, who both use yarn v1 lock files right now and are critical for the moderation team I'm probably missing something, but is there a reason upstream hasn't switched?
Could we ask them to? | 01:00:07 |
 Wanja Hentze | In reply to @adis:blad.is
Is this something that would be possible to add to fetchurl or a custom fetcher? yes | 01:01:00 |
| hexa | In reply to @adis:blad.is
I'm probably missing something, but is there a reason upstream hasn't switched?
Could we ask them to? switching to v2 locks would be problematic, as we lack the tooling to package them rn | 01:01:20 |
| hexa | we don't want them to switch at this time 🙂 | 01:01:30 |
| Wanja Hentze | In reply to @adis:blad.is
They're the same thing but the nix file expects packageRoot whereas the hook excepts npmRoot | 01:01:36 |
| @adis:blad.is | Ah, sorry for the misunderstanding =) | 01:01:42 |
| hexa | no worries 🙂 | 01:01:50 |
| Wanja Hentze | * In reply to @adis:blad.is
They're the same thing
but the nix file expects packageRoot whereas the hook expects npmRoot | 01:01:55 |
| Wanja Hentze | it seems to work if I pass the same value to both, but as a string to npmRoot and a path to packageRoot | 01:04:33 |
| Wanja Hentze | I tried a bunch of combinations before arriving at this one | 01:05:00 |
| @adis:blad.is | That's expected, though perhaps not entirely clear. | 01:07:46 |
 @ThorHop:matrix.org | Scwooly! So I want to get the astrojs language-server running through Kate LSP, but it isn't available in nixpkgs. What would be the easiest way to get a nodejs package in path? Is there a way to make global installs (i.e npm i -g) to install into a user path? Would it be better to just copy-paste another language-server nix definition? | 17:22:34 |
 Marie | the astro language server is in nixpkgs: nodePackages."@astrojs/language-server" | 17:28:52 |
| @ThorHop:matrix.org changed their display name from hopland (flaky frank) to hopland (evil entrepeneur). | 17:30:24 |
| @ThorHop:matrix.org changed their display name from hopland (evil entrepeneur) to hopland (nixpkgs-rolling when). | 18:25:13 |
| @ThorHop:matrix.org | In reply to @marie:marie.cologne
the astro language server is in nixpkgs: nodePackages."@astrojs/language-server" Thanks :D didn't know that. Also, had to remove with pkgs.nodePackages; to get it to work :/ so every line has pkgs.nodePackages now ^^; Dangit! And I got my nix files all nice and clean. But it's installed, now I just need to get it working. Again: Thanks! ^^ | 19:46:55 |
| 24 Nov 2023 |
 @ambroisie:belanyi.fr | Hey 👋
Anybody happen to have fixed this issue before:
Error: Cannot find module '@rollup/rollup-linux-x64-gnu'
| 18:35:55 |
| @ambroisie:belanyi.fr | (In #267320 for reference) | 18:36:06 |
| @ambroisie:belanyi.fr | It does appear in the yarn.lock, but does seem to be absent from /<<NIX>>/woodpecker-ci-modules-2.0.0/node_modules/ | 18:42:54 |
| 26 Nov 2023 |
 Sandro 🐧 | Try the new node builder that uses npm directly if that isn't already being used | 14:44:23 |
