Nix NodeJS | 202 Members | |
| 58 Servers |
| Sender | Message | Time |
|---|---|---|
| 3 Jan 2024 | ||
In reply to @janne.hess:helsinki-systems.de(that var just activates a sleeper agent we installed in npm to fix some of its broken behavior and inject vars when their fetcher lib re-execs the entirety of npm for git deps........) | 13:42:17 | |
In reply to @lily:lily.flowers(their coherence model for the moving parts of npm is utterly hecked) | 13:42:51 | |
| TIL about srcOnly | 13:44:27 | |
In reply to @lily:lily.flowersobviously :D | 13:44:47 | |
In reply to @lily:lily.flowers(and it re-execs npm without necessarily even ensuring lockfiles are coherent in the git dep and requiring them since it doesn't lock those needed deps in the original lockfile. and npm loves to silently get spooked, ignore the lockfile, and try to redownload literally everything..........) | 13:45:32 | |
| (oh and don't forget it drops the passed options when it re-execs. i mean come on, who needs those?) | 13:46:18 | |
| (at least they set an env var to ensure they don't accidentally recurisvely re-exec npm with no end, right?) | 13:46:39 | |
| (ugh npm makes me sad) | 13:46:44 | |
| (sorry for rant...) | 13:46:50 | |
In reply to @lily:lily.flowerstry yarn, might make you sadder | 13:47:30 | |
In reply to @janne.hess:helsinki-systems.dei doubt that tbh. sure it's missing some stuff we want for reproducibility, but at least it felt somewhat more intelligently designed | 13:48:04 | |
In reply to @lily:lily.flowers
| 13:48:19 | |
| and their solution to lockfile reproducibility involves actually sane locking that doesn't produce megabytes large dep trees | 13:48:26 | |
In reply to @janne.hess:helsinki-systems.de(not an error btw because I ran yarn dedupe first) | 13:48:49 | |
| (now if only their lockfile format was sane....) | 13:48:53 | |
In reply to @lily:lily.flowersit is with berry | 13:48:59 | |
In reply to @janne.hess:helsinki-systems.desaner, yeah | 13:49:06 | |
| tbh pnpm looks the most promising at this point by far | 13:49:20 | |
| yeah but it will take years for people to adapt that | 13:49:39 | |
| 13:49:44 | |
| bruh | 13:49:45 | |
| I will leave this here for future reference:
| 13:50:22 | |
this is what it took to fix it. thank you so much Lily Foster 🥳 | 13:52:16 | |
| Can't wait to push this >2GB package to the server :/ | 14:00:35 | |
| 6 Jan 2024 | ||
| 21:08:15 | ||
| 7 Jan 2024 | ||
| Hi, two things. First thing I am hoping to learn to package JS/TS programs, I am fairly early in my nix journey but have read through the nix pills and had a look through the manuals but I am finding the interop with npm lock files a bit of a blocker to my understanding. It seems as if the prevailing solution is to use “generators” to create nix files from the lock files, but I am unsure as to whether that is just for ad hoc packaging or if the same approach is used within This leads me on to the second thing which is that https://github.com/microsoft/vscode-js-debug seems to be included somewhere to be available to VSCode but I don’t think it’s available standalone from | 10:45:53 | |
| Heyo everyone, I'd like to tell nixpkgs's buildNpmPackage which node version to use: nodejs_21 in my case. How can I do it? I could override the https://github.com/NixOS/nixpkgs/blob/43eec8711993f851dc4f5dec16c0cb2fdb2b1d3a/pkgs/build-support/node/build-npm-package/default.nix#L4 | 19:02:40 | |
In reply to @pkolloch:matrix.org buildNpmPackage { ...; nodejs = nodejs_21; } | 19:03:51 | |
In reply to @lily:lily.flowersThank you! https://github.com/NixOS/nixpkgs/blob/43eec8711993f851dc4f5dec16c0cb2fdb2b1d3a/pkgs/build-support/node/build-npm-package/default.nix#L46 | 19:05:17 | |
| 9 Jan 2024 | ||
| 00:59:28 | ||