!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

211 Members
62 Servers

Load older messages


SenderMessageTime
12 Jan 2023
@winterqt:nixos.devWinter (she/her)Which is why I don't understand why it works on 14 and 18, but not 16.21:54:21
@winterqt:nixos.devWinter (she/her)That does not make sense21:54:25
@winterqt:nixos.devWinter (she/her)Unless they're mixing Nixpkgs revisions21:54:31
@lily:lily.flowersLily Foster
In reply to @winterqt:nixos.dev
Which is why I don't understand why it works on 14 and 18, but not 16.
I don't think it was 18. I assume they were on a recent enough commit that nodePackages was on 18 (because they mentioned not knowing where 14 came from)
21:55:06
@lily:lily.flowersLily Foster(So pretty sure it was only working on 14 for them, to clarify)21:55:29
@winterqt:nixos.devWinter (she/her)
In reply to @lily:lily.flowers
I don't think it was 18. I assume they were on a recent enough commit that nodePackages was on 18 (because they mentioned not knowing where 14 came from)
...so where does 14 come from, if their nodePackages is on 18? You're confusing me πŸ˜…
21:56:40
@lily:lily.flowersLily Foster
In reply to @winterqt:nixos.dev
...so where does 14 come from, if their nodePackages is on 18? You're confusing me πŸ˜…
It's not on 18 if they're on a commit that old (I briefly mistakenly thought it was but it's definitely not)
21:57:37
@winterqt:nixos.devWinter (she/her)So did it only work on 14 and they misspoke (or you misunderstood)? Because you said it's weird that it only didn't work on 16...21:58:19
@lily:lily.flowersLily Foster(Sry for confusion)21:58:32
@lily:lily.flowersLily Foster
In reply to @winterqt:nixos.dev
So did it only work on 14 and they misspoke (or you misunderstood)? Because you said it's weird that it only didn't work on 16...
Yes, I misunderstood
21:59:03
@lily:lily.flowersLily Foster* Yes, I misunderstood and it was only 1421:59:19
13 Jan 2023
@strum355:matrix.orgstroem - sourcegraph22.11 pin seems to use 16.18.1, which i think is exactly what I need. Bit unfortunate I couldnt overwrite the nodejs version on the older pin though πŸ€” I dont understand that exactly, has that issue been fixed since or is that still outstanding?12:47:20
@lily:lily.flowersLily Foster
In reply to @strum355:matrix.org
22.11 pin seems to use 16.18.1, which i think is exactly what I need. Bit unfortunate I couldnt overwrite the nodejs version on the older pin though πŸ€” I dont understand that exactly, has that issue been fixed since or is that still outstanding?
You would have needed to also use the new node-env.nix though, which is why just overriding nodejs didn't do what you needed
12:49:03
@lily:lily.flowersLily Foster
In reply to @strum355:matrix.org
22.11 pin seems to use 16.18.1, which i think is exactly what I need. Bit unfortunate I couldnt overwrite the nodejs version on the older pin though πŸ€” I dont understand that exactly, has that issue been fixed since or is that still outstanding?
You can do it with any nixpkgs pin after like mid-October, when all the dust settled on the nodePackages fixes
12:49:38
@strum355:matrix.orgstroem - sourcegraphnodejs always makes me sad, thanks for the help πŸ™‚12:52:11
@lily:lily.flowersLily Foster
In reply to @strum355:matrix.org
nodejs always makes me sad, thanks for the help πŸ™‚
Same πŸ™ƒ. Happy to help
12:52:49
@lily:lily.flowersLily Foster (To be clear, node2nix did not work with newer npm for a while so nodePackages was actually set to nodejs.pkgs.override { nodejs = nodejs-14_x; } to make it so that nodePackages didn't immediately break when nodejs was updated) 12:54:07
@lily:lily.flowersLily Foster(This was the PR to un-heck it: https://github.com/NixOS/nixpkgs/pull/193337)12:55:26
14 Jan 2023
@yuu:matrix.orgYuu Yin changed their display name from Yuu☯Yin to yuu.11:07:19
18 Jan 2023
@yuu:matrix.orgYuu Yin changed their display name from yuu to Yuu Yin.13:42:43
31 Jan 2023
@arteneko:matrix.org$nyx (it/its) joined the room.00:22:04
13 Feb 2023
@arteneko:matrix.org$nyx (it/its) changed their display name from Nyx (it/its) to $nyx (it/its).14:02:24
18 Feb 2023
@robert:funklause.dedotlambdaIs there a way to package a project using Yarn 3.3.1? I'm trying to build https://github.com/home-assistant/frontend from source and hit https://github.com/NixOS/nixpkgs/issues/148042 on the way.16:56:12
@winterqt:nixos.devWinter (she/her)not atm unless you use node2nix16:58:56
@robert:funklause.dedotlambda
In reply to @winterqt:nixos.dev
not atm unless you use node2nix
But that would only read package.json, not yarn.lock?
16:59:48
@winterqt:nixos.devWinter (she/her)you can nuke the yarn.lock and generate a lockfile from that17:00:52
@winterqt:nixos.devWinter (she/her) *npm lockfile with npm install 17:01:04
@winterqt:nixos.devWinter (she/her)

by that point you can just use fetchNpmDeps

though that lockfile size may be huge ugh

17:01:25
@robert:funklause.dedotlambdaHas anyone tried using https://github.com/imsnif/synp ? I wonder if it's deterministic17:01:25
@robert:funklause.dedotlambdaOh, same issue though: https://github.com/imsnif/synp/issues/9517:02:03

Show newer messages


Back to Room ListRoom Version: 6