| 11 Sep 2023 |
 Lily Foster | (Stuff like nix-ld and envfs or nix-alien are for when you have to accept that you'll have to run prebuilt binaries that aren't packaged sometimes) | 19:39:01 |
| Lily Foster | (Also I'm not sure what this has to do with node.js really but I'm glad I could help I guess) | 19:39:27 |
|  spion joined the room. | 19:41:41 |
| spion | 19:41:44 |
 @vid:matrix.org | oh that's interesting, thanks. I guess I still have to run a shell, but that's not too bad. Looking into it.
you're right this is probably more general than node.js, but though maybe there's a specific workaround for using playwright with its node.js library (rather than packaged standalone version).
| 19:41:45 |
| @vid:matrix.org | * oh that's interesting, thanks. I guess I still have to run a shell, but that's not too bad. Looking into it.
you're right this is probably more general than node.js, but thought maybe there's a specific workaround for using playwright with its node.js library (rather than packaged standalone version).
| 19:42:55 |
| @vid:matrix.org | hmm it looks like nix-ld … creates a symlink in /lib64 (-: but it expands on that | 19:45:21 |
| @vid:matrix.org | ok, it requires wrapping each binary. no idea how that would work with a binary called by a library. and going to be a headache for every program I try. starting to look like I'll have to do this kind of dev in a vm | 19:51:04 |
| 12 Sep 2023 |
|  @keiichi:matrix.org joined the room. | 11:28:11 |
|  ghpzin joined the room. | 11:33:24 |
| @vid:matrix.org | totally off the path now, but I wonder why chroot isn't used to solve these kinds of problems. seems more clean than nix-ld &c | 11:55:15 |
| @vid:matrix.org | * totally off the path now, but I wonder why chroot isn't used to solve these kinds of problems. seems more clean than nix-ld &c, which require piling hacks on hacks | 11:57:51 |
| Lily Foster | In reply to @vid:matrix.org
totally off the path now, but I wonder why chroot isn't used to solve these kinds of problems. seems more clean than nix-ld &c, which require piling hacks on hacks I mean I guess that's kinda what steam-run is (which is not steam-specific despite its name). Though that's technically bwrap, not chroot. Also now we're really getting away from being about nix node.js tooling 😛 | 11:59:32 |
| @vid:matrix.org | yes and no? a nodeJS developer wants to use NixOS to run arbitrary nodeJS related programs, especially maybe going into the age of wasm. In my experience, it takes that person far off their productive happy path into hairy weirdo spiders and snakes. I tried steam-run, it worked as well as my symlink hack, it worked until it stopped working. I mean nodeJS is already infamous for bad distractions. so if a great NixOS nodeJS DX is the desired outcome, I kinda feel it's on topic. except popping into a chroot as a solution is probably a solved problem somewhere else. | 12:05:08 |
| Lily Foster | Yeah. I guess the "running arbitrary executables that crummy tooling auto-downloads" is a problem independent of node.js though, even if it does show up in some node.js packages (off the top of my head vcpkg also does that, unfortunately) | 12:07:20 |
| @vid:matrix.org | one inflection might be this channel is for very NixOS specific development, whereas I'm talking about relating it to a general experience where if you have node/npm (or their equivalents) you're up for anything. NixOS specific development could be using a nix file instead of package.json, or nix specific directives, etc. | 12:07:33 |
