| 4 Aug 2023 |
Lily Foster | (Apologies that I only mostly have questionable ideas) | 20:54:00 |
gdamjan | I can't even say if the idea is questionable :) | 21:39:52 |
| 5 Aug 2023 |
gdamjan | is there documentation on nuke-references? | 16:39:48 |
Lily Foster | I hope there is in the nixpkgs manual. It might be nuke-references-to. I may be misremembering the name | 16:40:17 |
Lily Foster | In reply to @gdamjan:spodeli.org is there documentation on nuke-references? Looks like it's nukeReferences is the derivation and it's nuke-refs [-e ref-to-keep]* [files-to-remove-all-non-kept-references-from] | 16:46:33 |
Lily Foster | You also just do your own sed expression too tbh. It's a fairly simple script: https://github.com/NixOS/nixpkgs/blob/17544589b02100b9fa5c49fca82dfe489a060053/pkgs/build-support/nuke-references/nuke-refs.sh | 16:48:48 |
Lily Foster | If you'd rather the reference removal be inclusive rather than exclusive | 16:49:05 |
Lily Foster | For example | 16:49:09 |
| 8 Aug 2023 |
@me:indeednotjames.com | are we aware of this? https://nodejs.org/en/blog/vulnerability/august-2023-security-releases | 14:09:12 |
Lily Foster | In reply to @me:indeednotjames.com are we aware of this? https://nodejs.org/en/blog/vulnerability/august-2023-security-releases Yes I'm hoping marsam opens the PR when the release becomes public | 14:19:39 |
@me:indeednotjames.com | alright, thanks! :) | 14:20:36 |
Lily Foster | (Otherwise I might do it. Nodejs doesn't take too obscenely long on the aarch64 community builder, whereas it takes like an hour on my laptop) | 14:22:20 |
@gdesforges:matrix.org | Lily Foster: any luck looking at this? https://github.com/NixOS/nixpkgs/pull/244504 | 16:51:48 |
@gdesforges:matrix.org | the offlineCache error is a mystery to me | 16:52:20 |
@gdesforges:matrix.org | I'm wondering tho if it's not yet again an error with the damn resolutions field from packages.json | 16:53:10 |
@gdesforges:matrix.org | * I'm wondering tho if it's not yet again an error with the damn resolutions field from packages.json | 16:53:22 |
| countoren joined the room. | 18:42:33 |
countoren | Hi all, I am trying to build a npm project that depends on fortawesome font that are private the project has .npmrc with the authtoken, how can i make it work with either node2nix or buildNpmPackage? | 18:43:38 |
Lily Foster | In reply to @countoren:matrix.org Hi all, I am trying to build a npm project that depends on fortawesome font that are private the project has .npmrc with the authtoken, how can i make it work with either node2nix or buildNpmPackage? Hmmmm, can the auth token be set via environment variables? | 22:16:56 |
Lily Foster | I would say just allow that var impurely into the sandbox | 22:17:14 |
Lily Foster | You can configure that in the nix daemon | 22:17:20 |
Lily Foster | (also it will only work with buildNpmPackage -- node2nix does not inspect those tokens afaik) | 22:17:44 |
Lily Foster | In reply to @countoren:matrix.org Hi all, I am trying to build a npm project that depends on fortawesome font that are private the project has .npmrc with the authtoken, how can i make it work with either node2nix or buildNpmPackage? Oh actually it won't work with buildNpmPackage either... Can you open an issue on nixpkgs and @ me on it? (@lilyinstarlight) | 22:18:24 |
Lily Foster | I'll add it to our backlog of features | 22:18:28 |
Lily Foster | In reply to @gdesforges:matrix.org the offlineCache error is a mystery to me Yep, me too, since it's definitely in the cache. I'm assuming it's some difference in the cache naming between yarn2nix and fetchYarnDeps, which isn't supposed to happen but that was never regularly tested and I've already been concerned they had diverged a little | 22:19:20 |
Lily Foster | (I just started looking at it now, so I'm about to diff the cache dirs and find out) | 22:19:35 |
Lily Foster | In reply to @gdesforges:matrix.org the offlineCache error is a mystery to me Unless I'm misreading, the yarn.lock you committed is different from the upstream yarn.lock at 3.1.0...? | 22:29:36 |
Lily Foster | So I wonder if their lockfile was out of date or something | 22:29:52 |
@gdesforges:matrix.org | In reply to @lily:lily.flowers Unless I'm misreading, the yarn.lock you committed is different from the upstream yarn.lock at 3.1.0...? Well that could be a thing | 22:31:50 |
Lily Foster | Hmmm still doesn't work after updating to 3.2.0 | 22:32:16 |