!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

206 Members
59 Servers

Load older messages


SenderMessageTime
6 May 2023
@hexa:lossy.networkhexa

To see a list of supported npm commands, run:
npm help/electron-builder: No such file or directory

13:51:29
@hexa:lossy.networkhexacontinues like that13:51:31
@lily:lily.flowersLily FosterI guess I'll actually get out my laptop13:52:09
@ambroisie:belanyi.fr@ambroisie:belanyi.fr I saw tandoor-recipes in your list, just updated my version bump PR to use nodejs 😉 16:56:22
8 May 2023
@aktaboot:tchncs.deaktaboot joined the room.20:44:24
@aktaboot:tchncs.deaktaboot
In reply to @lily:lily.flowers
We, uh, should probably make tooling to handle those soon
can I open an issue about this ? 👀
20:53:07
@lily:lily.flowersLily Foster
In reply to @aktaboot:tchncs.de
can I open an issue about this ? 👀
Yeah, I can do that in a bit
21:01:51
9 May 2023
@denbrahe:matrix.org@denbrahe:matrix.org joined the room.10:30:01
@denbrahe:matrix.org@denbrahe:matrix.org Hi, I'm trying to create a derivation for a React package using buildNpmPackage. However, both buildNpmPackage and prefetch-npm-deps always fail with Error: https://registry.npmjs.org/@babel/eslint-parser/-/eslint-parser-7.19.1.tgz: Connection Failed: tls connection init failed: Connection reset by peer (os error 104). Which package failed varies between retries. What could cause that? 10:34:20
@lily:lily.flowersLily Foster
In reply to @denbrahe:matrix.org
Hi, I'm trying to create a derivation for a React package using buildNpmPackage. However, both buildNpmPackage and prefetch-npm-deps always fail with Error: https://registry.npmjs.org/@babel/eslint-parser/-/eslint-parser-7.19.1.tgz: Connection Failed: tls connection init failed: Connection reset by peer (os error 104). Which package failed varies between retries. What could cause that?
Sometimes the registry connection fails or gets dropped on wifi for me. Retry until it works I guess. I plan to add retry logic to the fetcher so those transient error don't cause the entire fetch to fail
10:46:39
@lily:lily.flowersLily Foster It fetches in parallel, so you might be able to set --cores 1 on the nix build command to disable that (I forget if it respects that or not) 10:47:14
@denbrahe:matrix.org@denbrahe:matrix.org Ok, thank you! If I understand correctly, prefetch-npm-deps adds the cache to the Nix store, so if I get prefetch-npm-deps to work buildNpmPackage should also work? 10:52:13
@lily:lily.flowersLily FosterIt does not add it to the store by default10:56:12
@lily:lily.flowersLily FosterYou'd have to actually use nix build for it to go to the store10:56:32
@denbrahe:matrix.org@denbrahe:matrix.orgOkay, I'll just loop nix-build then. Thanks!10:57:49
@lily:lily.flowersLily Foster Try --cores 1 on your nix-build command if you haven't already, since that might help 10:58:45
@lily:lily.flowersLily Foster (Or maybe it's only --option cores 1 for the old cli... i forget) 10:59:11
@denbrahe:matrix.org@denbrahe:matrix.orgI'll try both 😛11:03:40
@denbrahe:matrix.org@denbrahe:matrix.org100 retries, got nothing. Is this normal? It's a small project, only notable deps are react and typescript11:32:01
@lily:lily.flowersLily FosterNope that's not normal. I'll see if I can get retry logic working today and will let you try it, if you can't get a successful build before then11:42:27
@lily:lily.flowersLily FosterAlso if it's ignoring nix's NUM_JOBS setting then I'll fix that too11:42:42
@aktaboot:tchncs.deaktaboot
In reply to @lily:lily.flowers
Yeah, I can do that in a bit

opened an issue,

Do you know what needs to be done for that to work ? I am not sure where the parsing functions for yarnLock are defined, I guess we would add a yarnLock2 or yarnLockv2 for the newer version

13:57:11
@lily:lily.flowersLily FosterIt uses upstream @yarnpkg/lockfile, but an older pre-berry version13:58:44
@aktaboot:tchncs.deaktabootberry is newer ?14:00:07
@lily:lily.flowersLily FosterYes. Yarn 2+ is berry14:02:52
@aktaboot:tchncs.deaktaboot
In reply to @lily:lily.flowers
Yes. Yarn 2+ is berry
does that seems more like a package upstream issue ?
14:04:32
@lily:lily.flowersLily Foster It's not an upstream issue, we don't use the upstream parser yet. I haven't tried to see if that's the only requirement for fetchYarnDeps to work 14:07:53
@lily:lily.flowersLily Fosteryarn2nix is hecked for berry though14:08:00
@aktaboot:tchncs.deaktaboot(also I'm not trying to put pressure on you in any way :), I just wanted to open an issue for the record and other people to see eventually)14:08:23
@aktaboot:tchncs.deaktaboot
In reply to @lily:lily.flowers
yarn2nix is hecked for berry though
oh, is there ongoing work on that ? 👀
14:09:11

Show newer messages


Back to Room ListRoom Version: 6