Nix NodeJS | 193 Members | |
| 57 Servers |
| Sender | Message | Time |
|---|---|---|
| 15 Jan 2025 | ||
| That does work | 03:41:43 | |
| 19:02:28 | ||
| 16 Jan 2025 | ||
| 01:28:40 | ||
Hi, can someone tell what is the preferred way of packaging a Node.js CLI in nixpkgs? Should I add it to pkgs/development/node-packages/node-packages.json or use buildNpmPackage? | 02:14:21 | |
| latter | 02:16:10 | |
| Thanks, I'm glad because I tried the first method and it wasn't working 😅 | 02:16:47 | |
Okay, followup question, the package I'm building has an npm run build script, but it's just defined as npm run lint && npm run test, should I set dontNpmBuild = true so that nix doesn't lint and test the package every time it builds? | 02:39:45 | |
| Here's the PR for the package if anyone has suggestions :) https://github.com/NixOS/nixpkgs/pull/374206 | 04:26:42 | |
| 18 Jan 2025 | ||
| 14:55:16 | ||
| Hey there. I am trying to build https://github.com/gristlabs/grist-core bad sadly I have no clue what I am doing. | 14:57:06 | |
| From perusing nixpkgs my take away was that the current best approach are yarn* hooks. | 14:57:50 | |
| So I copied the element-call derivation which seems to be doing exactly that. | 14:58:12 | |
| Now I get this error: | 14:58:26 | |
| 14:58:51 | |
*
| 14:59:03 | |
| If there are any docs about how to do this properly please let me know. | 14:59:53 | |
| The error looks surprisingliy like https://github.com/nix-community/yarn2nix/issues/111 | 15:12:27 | |
| That url is pretty clearly wrong. | 15:12:44 | |
| 19:16:59 | ||
| Hey, is there a recommended way to develop a npm/nodejs app now ? (node2nix and npmlock2nix seem unmaintained, and this post https://discourse.nixos.org/t/how-to-use-importnpmlock/53878/2 has no response) thank you all | 19:26:32 | |
ok buildNpmPackage seems to do the job | 20:21:01 | |
| 20 Jan 2025 | ||
| hey, question, any ideas why yarn would fail out trying to read /yarn/config? | 16:48:46 | |
| running any yarn command at all results in this: | 16:49:34 | |
| 26 Jan 2025 | ||
| 00:35:26 | ||
| Hey, anyone here ever experienced issues with Vite or especially Astro not hot-reloading when a nix flake generated symlink (say a .pre-commit-config.yaml for example) is present? Every attempt to tell vite to ignore this file fails unfortunately. When I delete said symlinks HMR works again immediately. | 00:39:01 | |
| sounds like a bug in Vite or Astro (or more specifically the dependency they both use for HMR) | 00:52:25 | |
| Just tried to reproduce this in a small VIte project, guess thats an Astro Bug | 00:59:22 | |
| I cant reproduce it in Vite | 00:59:29 | |
| Well, I guess I'll open an issue in the Astro project then | 00:59:53 | |
| Btw. since describing it is rather unspecific. If you want to reproduce:
It does HMR when I will try to test if I can get choickbar (Vites HMR file watcher) to fail as well, but I don't have high hopes since I cannot reproduce this in Vite either. | 01:21:31 | |