!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

206 Members
59 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
21 Jul 2023
@ulli:hrnz.li@ulli:hrnz.li2023-04-2009:24:46
@hellwolf:matrix.orghellwolfhuh09:30:53
@hellwolf:matrix.orghellwolfaha, of course09:31:12
@hellwolf:matrix.orghellwolfpkgs/top-level/aliases.nix <-- they are aliases, okay09:32:14
@hellwolf:matrix.orghellwolfI should use 'nodejs_18' instead, not nodejs-16_x09:32:51
22 Jul 2023
@gdamjan:spodeli.orggdamjan
In reply to @lily:lily.flowers
Ah, yarn2nix makes me sad 🥲
what would be an alternative approach?
15:59:34
23 Jul 2023
@lily:lily.flowersLily Foster
In reply to @gdamjan:spodeli.org
what would be an alternative approach?
buildYarnPackage, whenever we come back to that. It's like next on the list after a few more buildNpmPackage/fetchNpmDeps PRs I have open (see the Node.js team project board)
00:08:12
@lily:lily.flowersLily Foster(there's no major technical blockers, it just needs some time put into it, and we've been dealing with too much real-life nonsense 😭)00:10:06
@sandro:supersandro.deSandro 🐧 joined the room.21:51:42
@sandro:supersandro.deSandro 🐧How do we package things that require yarn berry? Hedgedoc is currently stuck on 1.9.7 because of that and there is soon an urgency to update.21:51:58
@lily:lily.flowersLily FosterIf I get the time and mental bandwidth, I may take a stab at it this week. Right now we have no tooling for it so just generating and vendoring a package-lock.json is unfortunately probably the best solution atm if it still builds fine with npm22:00:40
@me:indeednotjames.com@me:indeednotjames.com joined the room.22:12:48

Show newer messages


Back to Room ListRoom Version: 6