!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

209 Members
59 Servers

Load older messages


SenderMessageTime
30 May 2023
@lily:lily.flowersLily FosterThere 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:rory.gayEmma [it/its]ah12:24:03
1 Jun 2023
@drupol:matrix.orgPolAnybody 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
@drupol:matrix.orgPolThe pr is here: https://github.com/NixOS/nixpkgs/pull/23428909:21:23
@drupol:matrix.orgPol * 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
@drupol:matrix.orgPol * 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:tapesoftware.netraphi changed their display name from raphi to raphi (element unread channel fix when).13:03:14
@adam:valkor.netadamcstephensLooks like you're blocked on nodejs18 and the upstream support?13:25:50
2 Jun 2023
@drupol:matrix.orgPol No, I must use NodeJS 16. There's no support of NodeJS 18 in coder/code-server yet. 06:45:18
@drupol:matrix.orgPolI have another question for NodeJS maintainers, if any here.06:45:30
@drupol:matrix.orgPolI 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
@adam:valkor.netadamcstephens
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
@adam:valkor.netadamcstephensWould we consider reverting that change for master/unstable until 16 actually becomes EOL in September?13:24:11
@lily:lily.flowersLily 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:lily.flowersLily 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:lily.flowersLily 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:lily.flowersLily 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:lily.flowersLily Foster(And still am a tad skeptical)13:37:48
@raitobezarius:matrix.orgraitobezariusWe opened an issue on affected packages for Node.js 1613:37:54
@raitobezarius:matrix.orgraitobezariusIMHO, 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 least13:38:08
@raitobezarius:matrix.orgraitobezariusNo matter what, we will find ourselves in September pretty quickly and given my experience with saying hi to upstream, they need time to accomodate13:38:27
@raitobezarius:matrix.orgraitobezariusAdding a simple permittedInsecurePackages in the meantime is not too shocking and we allowed caching exceptions for Node.js 16 and OpenSSL 1.1 to make the ride less bumpy for everyone13:38:47
@lily:lily.flowersLily FosterYeah it's an upstream issue anyway. If your package needs 16, you can just enable insecure packages in nixpkgs 🤷‍♀️13:39:02
@adam:valkor.netadamcstephens Yeah I figured we wouldn’t want to revert, just putting the question out there. 13:39:46
@lily:lily.flowersLily Foster
In reply to @raitobezarius:matrix.org
We opened an issue on affected packages for Node.js 16
Oh really? Yeah how many are left? (Also were node maintainers pinged on that issue I don't remember seeing one other than the lists on the PR 🤔)
13:40:04
@raitobezarius:matrix.orgraitobezariusairfield, base16-builder, netlify-cli, spacegun, n8n?13:40:35
@raitobezarius:matrix.orgraitobezariusare the remaining ones13:40:39
@raitobezarius:matrix.orgraitobezariuswait I'm not uptodate on master13:40:54
@lily:lily.flowersLily FosterOkay that's not too bad. I thought netlify was already handled though13:40:58
@lily:lily.flowersLily FosterAnd spacegun has been broken well before the 16 deprecation iirc13:41:13

Show newer messages


Back to Room ListRoom Version: 6