!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

209 Members
60 Servers

Load older messages


SenderMessageTime
12 Sep 2023
@lily:lily.flowersLily Foster
In reply to @lily:lily.flowers
(I take that back. It doesn't work for the systemd test suite so I do keep a fedora vm around for that)
(Systemd test suite has pretty deep system and kernel expectations that must be met. Someone was working on a NixOS test framework setup that runs it though)
12:34:35
@lily:lily.flowersLily Foster
In reply to @lily:lily.flowers
Yeah your pov is appreciated! I just wish I had better answers
(If you do find something that helps developer DX for this, do send it over to awesome-nix to make it more discoverable for people too!)
12:38:28
@lily:lily.flowersLily Foster* (If you do find something that helps developer experience for this, do send it over to awesome-nix to make it more discoverable for people too!)12:38:45
@vid:matrix.org@vid:matrix.orgI would love to, but have to put it aside right now. nixos is a means to an end for me, not the end.12:38:59
@lily:lily.flowersLily Foster(Also I was kinda suggesting asking in a more general channel because people a lot smarter than me are more likely to give you better answers there 😅)12:42:31
@vid:matrix.org@vid:matrix.orgmaybe when I have more time. I'm very happy with nixos otherwise. and since I use workspaces with hotkeys, having to use a vm is not the end of the world.12:46:57
@vid:matrix.org@vid:matrix.org * maybe when I have more time. I'm very happy with nixos otherwise. and since I use workspaces with hotkeys and x-forwarding, having to use a vm is not the end of the world.12:49:12
@vid:matrix.org@vid:matrix.org * maybe when I have more time. I'm very happy with nixos otherwise. and since I use workspaces with hotkeys and x-forwarding, having to use a vm is not the end of the world. it is a pretty convoluted setup, though.12:50:29
@vid:matrix.org@vid:matrix.org * maybe when I have more time. I'm very happy with nixos otherwise. and since I use workspaces with hotkeys and x-forwarding, having to use a vm is not the end of the world. it is a pretty convoluted setup, though. but that will only get worse if I start tailouring the repo to the OS.12:51:56
@yaya:uwu.isyaya joined the room.14:19:26
@vid:matrix.org@vid:matrix.orgRedacted or Malformed Event14:28:47
@vid:matrix.org@vid:matrix.org *

what's happening here?


changed 33 packages in 1s
vid@kkvm /mnt/space/home/vid/D$ nodemon
nodemon: command not found
vid@kkvm /mnt/space/home/vid/D$ node -v
v18.17.1
vid@kkvm /mnt/space/home/vid/D$ which node```
/run/current-system/sw/bin/node

14:28:53
@vid:matrix.org@vid:matrix.org

something I should know here?

vid@kkvm /mnt/space/home/vid/D$ npm i -g nodemon

changed 33 packages in 1s
vid@kkvm /mnt/space/home/vid/D$ nodemon
nodemon: command not found
vid@kkvm /mnt/space/home/vid/D$ node -v
v18.17.1
vid@kkvm /mnt/space/home/vid/D$ which node
/run/current-system/sw/bin/node

14:30:03
@vid:matrix.org@vid:matrix.orgoic, also "no the nixos way"14:31:48
@vid:matrix.org@vid:matrix.org * oic, also "not the nixos way"14:33:14
13 Sep 2023
@mkg20001:mkg20001.iomkg20001 joined the room.09:18:14
15 Sep 2023
@vid:matrix.org@vid:matrix.orgI think I found a good solution, distrobox. I used the unstable channel, separate home directory, hard coded my PATH (even though latest distrobox is not supposed to include host binaries). don't want to push my luck so knock wood, but I've been able to use it like a distinct environment, including x11 forwarding to the host, which is the dream12:51:07
@vid:matrix.org@vid:matrix.orgiow I'm living the dream12:51:27
@vid:matrix.org@vid:matrix.orgcould have just used containers on their own but this takes away a lot of the wtf12:52:20
21 Sep 2023
@dedmunwalk:matrix.orgdedmunwalk joined the room.23:09:32
22 Sep 2023
@bl1nk:matrix.orgbl1nk changed their profile picture.11:21:29
@bl1nk:matrix.orgbl1nk changed their profile picture.11:23:14
@mkg20001:mkg20001.iomkg20001there is nodePackages.nodemon, you can install it via nix profile install nixpkgs#nodePackages.nodemon15:22:05
@hexa:lossy.networkhexa
node_modules/rimraf
node_modules/finalhandler/node_modules/ms
node_modules/@histoire/app
Error: unknown error

Caused by:
    [56] Failure when receiving data from the peer
22:41:10
@hexa:lossy.networkhexa😿22:41:13
@hexa:lossy.networkhexatransient22:43:15
@lily:lily.flowersLily FosterIt's supposed to be doing retries :(22:55:31
@lily:lily.flowersLily Foster
In reply to @hexa:lossy.network
transient
Can you try with RUST_LOG=info in the environment and get it to happen, so I can see if retries are working?
22:56:36
@hexa:lossy.networkhexait worked on my third retry22:57:00
@hexa:lossy.networkhexahence transient 🙂22:57:07

Show newer messages


Back to Room ListRoom Version: 6