| 13 Apr 2024 |
 Cobalt | * What are you looking for in particular? Packaging, development shell(s) or something else? | 13:26:40 |
 Tumble | Changing my workflow to involve flakes? | 13:28:35 |
 Lily Foster | In reply to @tumble1999:matrix.org
Changing my workflow to involve flakes? what are you wanting flakes to get you? using flakes just for using flakes won't automatically give you much | 13:30:11 |
| Tumble | packages are only installed when nececery
like if i used rust one day, cargo and rust up will be in my system
when i stop developing in rust for a but it will eventialy stop being installed on mys system
when i develop with js, node things would be installed,
when i take a break, they will eventialy stop being installed on my system
thats how i see it
also if i go on anouther system (that doesnt have nixos but does have nix), i wont have to install stuff just use the flake and everything will set its self up | 13:41:51 |
 avocadoom | I guess you confuse flakes with shells. Shells are not coupled with flakes. You don't need to understand the concept of flakes to use shells | 13:43:37 |
| Tumble | flakes let you get specific versions of things though dont they | 13:45:56 |
| avocadoom | Sure you can pin nixpkgs, though you can also do this with standard nix derivations | 13:49:59 |
| Tumble | also using a flake with my nixos config makes channels easier to manage | 13:51:03 |
| Cobalt | Using flakes for devshells is a good approach ime. For nodejs you don't need anything special in most projects. Just use a normal devshell inside a flake and use the relevant packages, like `nodejs`, as build inputs. | 13:55:50 |
| Cobalt | There are also some more elaborate setups possible, like setting a specific nodejs version for your nixpkgs instance used in the devshells. | 13:57:55 |
| Tumble | would it ever need to go in .packages/.app for doing stuff like nix run | 13:59:03 |
| Cobalt | `nix run` stuff is the `apps` output iirc. | 13:59:34 |
| Tumble | i think nix dev applys to devshells though falls back to app and then package
and nix run applyes to app and falls back to package | 14:00:18 |
| Lily Foster | In reply to @c0ba1t:matrix.org
`nix run` stuff is the `apps` output iirc. both apps and packages | 14:00:45 |
| Tumble | nix build .packages
nix run .app .packages
nix develop .devShells .app .packages
nix init .templates | 14:02:00 |
| Tumble | * nix build .packages
nix run .apps .packages
nix develop .devShells .apps .packages
nix init .templates | 14:02:17 |
|  @alex3829:matrix.org joined the room. | 16:04:46 |
| 15 Apr 2024 |
|  aktaboot joined the room. | 10:45:29 |
| 16 Apr 2024 |
|  pareto-optimal-dev joined the room. | 16:46:31 |
| pareto-optimal-dev | Why can't I require('@mongosh/autocomplete'); in nix install mongosh? I see that it is run like:
exec "/nix/store/4r6qr0bzmkdjjjaf7i4vbjmf92l9zpq0-nodejs-20.11.1/bin/node" /nix/store/wzh6cmr5xnzg1ljsvfwpl2ph7iws5sxw-mongosh-2.2.2/lib/node_modules/mongosh/bin/mongosh.js "$@"
I see that /nix/store/wzh6cmr5xnzg1ljsvfwpl2ph7iws5sxw-mongosh-2.2.2/lib/node_modules/mongosh/bin/mongosh.js has:
#!/nix/store/4r6qr0bzmkdjjjaf7i4vbjmf92l9zpq0-nodejs-20.11.1/bin/node
require('@mongosh/cli-repl/lib/run');
I guess I somehow need to add my require for mongosh/autocomplete to that mongosh.js file? I thought that because /nix/store/wzh6cmr5xnzg1ljsvfwpl2ph7iws5sxw-mongosh-2.2.2/lib/node_modules/mongosh/node_modules/@mongosh/autocomplete/ exists I could do require @mongosh/autocomplete.
| 16:51:18 |
| 17 Apr 2024 |
| @alex3829:matrix.org changed their display name from alex3829 to real_z22. | 04:36:36 |
| @alex3829:matrix.org changed their display name from real_z22 to real_z2. | 05:34:06 |
| 25 Apr 2024 |
|  @me:indeednotjames.com left the room. | 03:36:37 |
| Cobalt | Hi, does someone know how get buildNpmPackage working with npm workspaces? It appears to not properly merge the node_modules from the workspace and the root, resulting in missing dependencies | 16:00:26 |
| Lily Foster | In reply to @c0ba1t:matrix.org
Hi, does someone know how get buildNpmPackage working with npm workspaces? It appears to not properly merge the node_modules from the workspace and the root, resulting in missing dependencies it does handle them (assuming they are npm workspaces and not the fake ones lerna and such mash together) | 16:17:37 |
| Lily Foster | can you share derivation? | 16:17:41 |
| Cobalt | In reply to @lily:lily.flowers
can you share derivation? https://git.tu-berlin.de/proveit/proveit.nix/-/blob/main/pkgs/proofbuddy.nix?ref_type=heads#L89 | 16:20:59 |
| Cobalt | I can also share the package.json files but the source code is unfortunately not public | 16:21:18 |
| Lily Foster | yes, please share the package.json of the root workspace dir, of the workspace package, and the package-lock.json of the root workspace dir | 16:22:00 |
| Lily Foster | (you can DM if you prefer) | 16:22:08 |
