!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

213 Members
63 Servers

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


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.orgdenbrahe joined the room.10:30:01
@denbrahe:matrix.orgdenbrahe 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.orgdenbrahe 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.orgdenbraheOkay, 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

Show newer messages


Back to Room ListRoom Version: 6