!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

209 Members
59 Servers

Load older messages


SenderMessageTime
2 Jun 2023
@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
@raitobezarius:matrix.orgraitobezariusapologies13:41:30
@lily:lily.flowersLily Foster
In reply to @lily:lily.flowers
Okay that's not too bad. I thought netlify was already handled though
(Pretty sure I merged Robert's PR for that)
13:41:36
@raitobezarius:matrix.orgraitobezariuswe only have netlify-cli left on master13:41:36
@raitobezarius:matrix.orgraitobezariusthen someone forgot to update the generate.sh13:41:50
@lily:lily.flowersLily FosterOh maybe I'm misremembering then13:41:50
@raitobezarius:matrix.orgraitobezariusfor netlify-cli13:41:52
@lily:lily.flowersLily FosterOh13:41:57
@lily:lily.flowersLily Fosterrip13:41:59
@raitobezarius:matrix.orgraitobezariusit will still generate with nodejs-16 for the next upgrade13:41:59
@raitobezarius:matrix.orgraitobezariusbut it's true that we don't have netlify cli with nodejs 16 anymore13:42:10
@raitobezarius:matrix.orgraitobezariusso in fact13:42:11
@raitobezarius:matrix.orgraitobezariusonly codeserver shit is nodejs16 ?13:42:16
@raitobezarius:matrix.orgraitobezariusthis is definitely not worth a rollback13:42:21
@lily:lily.flowersLily Foster
In reply to @raitobezarius:matrix.org
it will still generate with nodejs-16 for the next upgrade
I didn't notice that in the PR, oops 😅
13:42:25
@raitobezarius:matrix.orgraitobezariusno worries!13:42:29
@raitobezarius:matrix.orgraitobezariuswe have the same thing for nodejs-16 actually on some packages13:42:39
@raitobezarius:matrix.orgraitobezarius * we have the same thing for nodejs-14 actually on some packages13:42:42
@lily:lily.flowersLily FosterI just commented on the netlify PR13:44:45
@drupol:matrix.orgPolI though that would be a game changer, but... It's not.14:40:57
@lily:lily.flowersLily Foster
In reply to @drupol:matrix.org
I though that would be a game changer, but... It's not.
Has upstream confirmed they intend to support 18+ soon? You can still use codeserver, it's just gonna be marked insecure. Hydra is even still building it
14:49:19
@drupol:matrix.orgPolWhen a derivation requires an insecure dependency, is it also marked insecure ?14:50:31
@drupol:matrix.orgPol Since openvscode-server and code-server both relies on VSCode, and since VScode doesn't support Node JS 18 yet, ... it's impossible to use Node JS 18 with them. 14:52:24
@drupol:matrix.orgPol * Since openvscode-server and code-server both inherit the VSCode source code, and since VScode doesn't support Node JS 18 yet, ... it's impossible to use Node JS 18 with them. 14:52:47

Show newer messages


Back to Room ListRoom Version: 6