Nix NodeJS | 212 Members | |
| 61 Servers |
| Sender | Message | Time |
|---|---|---|
| 3 May 2026 | ||
| Redacted or Malformed Event | 14:08:52 | |
| 7 May 2026 | ||
| 17:52:11 | ||
| 8 May 2026 | ||
| 08:42:29 | ||
| 20:54:34 | ||
| 20:54:42 | ||
| 16 May 2026 | ||
| 18:35:25 | ||
| 19 May 2026 | ||
| 20:56:23 | ||
| 26 May 2026 | ||
| 11:40:26 | ||
| 29 May 2026 | ||
| 07:06:09 | ||
| 1 Jun 2026 | ||
| 04:32:17 | ||
| 4 Jun 2026 | ||
| 04:22:41 | ||
| 7 Jun 2026 | ||
| 20:35:09 | ||
| 9 Jun 2026 | ||
| 22:50:07 | ||
| I'm not sure how much this'll impact nixpkgs, but I'd rather let people know early https://github.blog/changelog/2026-06-09-upcoming-breaking-changes-for-npm-v12/ | 22:51:30 | |
| 10 Jun 2026 | ||
| i think we already disable scripts by default since many access the network | 00:06:27 | |
| I'm experimenting with adding a nix package to nexus mods' Vortex repo: https://github.com/MattSturgeon/Vortex/tree/nix-package It uses pnpm, but my current package is failing with:
which almost seems like | 15:27:38 | |
| An ugly way to find out what that flag is being passed to is to add
| 18:43:52 | |
| Also make sure to use fetcherVersion = 4, as version 3 is not reproducible across different systems with pnpm 11 | 19:10:28 | |
| This is what I got
I assume the random empty string is the culprit | 19:11:07 | |
Yup. Removing the pnpmInstallFlags attribute fixes it | 19:12:05 | |
Another opportunity for me to mention my importPnpmLock.nix library (GitHub mirror) It's similar to importCargoLock, importNpmLock and others from Nixpkgs, though this one sadly only works using IFD, as your I have been using it at my workplace to build and package our Node apps using Nix. Without it, I wouldn't really be able to use Renovate bot very comfortably | 19:16:56 | |
| Ah, I'll probably need to bump nixpkgs too then; they have a nixpkgs pinned that says "unrecognized version, use 1, 2, or 3". Also, the Nixpkgs manual is still saying "version 3 is recommended for new packages", does that need updating? | 19:40:21 | |
Ah, enabling structuredAttrs seems to resolve that too; looks like empty flags list -> empty shell string with non-structured-attrs is buggy. Probably need to use stdenv's concatTo helper to normalize the flags array in the hook. | 19:45:18 | |
| The configure phase seems to be working now (pushed), thanks for the help! Now, two of build steps are failing. One of them ( https://github.com/Nexus-Mods/Vortex/blob/master/src/main/download-duckdb-extensions.ts The other one (
https://github.com/Nexus-Mods/Vortex/blob/master/extensions/theme-switcher/build.mjs | 20:48:53 | |
| 11 Jun 2026 | ||
| * The configure phase seems to be working now (pushed), thanks for the help! Now, two of build steps are failing. One of them ( https://github.com/Nexus-Mods/Vortex/blob/master/src/main/download-duckdb-extensions.ts EDIT: The first one I've worked-around with a fixed-output-derivation, but really needs upstream refactoring to improve how they fetch duckdb-extensions. The second one needed node-gyp to build a transitive dependency, oddly, I needed to run node-gyp manually in
https://github.com/Nexus-Mods/Vortex/blob/master/extensions/theme-switcher/build.mjs | 04:02:04 | |
| * The configure phase seems to be working now (pushed), thanks for the help! Now, two of build steps are failing. One of them ( https://github.com/Nexus-Mods/Vortex/blob/master/src/main/download-duckdb-extensions.ts EDIT: The first one I've worked-around with a fixed-output-derivation, but really needs upstream refactoring to improve how they fetch duckdb-extensions. The second one needed node-gyp to build a transitive dependency, oddly, I needed to run node-gyp manually in
https://github.com/Nexus-Mods/Vortex/blob/master/extensions/theme-switcher/build.mjs EDIT: The first one I've worked-around with a fixed-output-derivation, but really needs upstream refactoring to improve how they fetch duckdb-extensions. The second one needed node-gyp to build a transitive dependency, oddly, I needed to run node-gyp manually in | 04:02:28 | |
| 5 Dec 2022 | ||
| 14:44:17 | ||
| Thanks | 14:44:25 | |
In reply to @hexa:lossy.networkit doesn't look like he read the message, are you sure it wasn't just your server syncing the history :P | 14:45:19 | |
| ? | 14:45:48 | |