Sender | Message | Time |
---|---|---|
5 Nov 2024 | ||
In reply to @vengmark2:matrix.orgyou don't, it doesn't make as much sense in the context of npm | 22:22:30 | |
In reply to @lily:lily.flowersHow do I achieve the same thing then, a self-contained node executable with a given set of packages? | 22:23:40 | |
node operates with node_modules folders, i guess you can make such a thing if you wanna add stuff to lib/node_modules , but what's your goal? | 22:31:26 | |
yeah it's a request that doesn't quite compute as a concrete technical need, with how npm works | 22:32:51 | |
* yeah it's a request that doesn't quite compute to a concrete technical need, with how npm works | 22:34:21 | |
7 Nov 2024 | ||
So if I install an NPM package globally, that won't be available in a project Nix shell? | 09:36:26 | |
depends | 10:40:30 | |
In reply to@vengmark2:matrix.orgThat depends on if the shell is --pure or not. It also depends on the shell configuration (doesn't NPM install executables into a separate directory?) | 19:32:22 | |
That depends on if the shell is --pure or not. It also depends on the user's shell configuration if the shell is impure (doesn't NPM install executables into a separate directory?) | 19:51:38 | |
In reply to @tomodachi94:matrix.orgAh, that clarifies it, and shows a real use case: Doing pkgs.python310.withPackages (ps: [ps.numpy]) in a Nix shell in a Python project ensures that I get a specific Python interpreter version with a specific package set, with no need for having to develop in a pure shell. Being able to do the same thing with Node.js would be great: pkgs.nodejs_X.withPackages (ps: [ps.foo]) would result in having a specific Node.js interpreter version and a specific package set, with no worries about interference from globally installed packages. | 19:53:19 | |
Iirc impure shells should prepend to the PATH, so explicitly specifying the packages should work if they're packaged | 23:48:41 | |
* Iirc impure shells should prepend to the PATH, so explicitly specifying the packages should work if they're packaged in Nix | 23:56:16 | |
8 Nov 2024 | ||
14:28:48 | ||
14:30:07 | ||
10 Nov 2024 | ||
04:44:48 | ||
16 Nov 2024 | ||
06:22:03 | ||
18 Nov 2024 | ||
08:03:12 | ||
Could I make a node js service call the nixos-rebuild command? | 12:14:00 | |
You can? It's just an executable (script). You might need elevated permission though. | 13:03:30 | |
* You can. It's just an executable (script). You might need elevated permission though. | 13:04:19 | |
Tumble: it's a bash script, so to call it 'safely' (insofar it can be called safely) you'd call it as childProcess.spawn("bash", [ "/path/to/nixos-rebuild", "switch" ]) or something along those lines | 13:16:06 | |
taking into account that something that controls what gets rebuilt has essentially root access | 13:16:19 | |
28 Nov 2024 | ||
13:47:24 | ||
Hey everybody, I have a friend running into this issue on his linux machine: https://gist.github.com/drupol/58bab21103636f622bb3a623850ca0b3 | 13:47:46 | |
Is there something I can try to help him? | 13:50:19 | |
In reply to@drupol:matrix.orgIf you still need help, it just means they OOMd while running it: 3: 0xe7d2a4 v8::internal::V8::FatalProcessOutOfMemoryIt should show up better on the in logs before that with something like: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory | 15:44:32 | |
If you still need help, it just means they OOMd while running it:3: 0xe7d2a4 v8::internal::V8::FatalProcessOutOfMemoryIt should show up better in logs before that with something like: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory | 15:44:51 | |
<del>If you still need help, it just means they OOMd while running it:3: 0xe7d2a4 v8::internal::V8::FatalProcessOutOfMemoryIt should show up better in logs before that with something like: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory </del>Run it myself and node needs more than default memory for whatever open-webui is doing.With env.NODE_OPTIONS = "--max-old-space-size=8192"; it seems to build. | 16:14:05 | |
~If you still need help, it just means they OOMd while running it:3: 0xe7d2a4 v8::internal::V8::FatalProcessOutOfMemoryIt should show up better in logs before that with something like: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory ~Run it myself and node needs more than default memory for whatever open-webui is doing.With env.NODE_OPTIONS = "--max-old-space-size=8192"; it seems to build. | 16:14:34 | |
Run it myself and node needs more than default memory for whatever open-webui is doing.With env.NODE_OPTIONS = "--max-old-space-size=8192"; it seems to build. | 16:14:54 |