| 15 Oct 2023 |
|  felschr joined the room. | 20:53:53 |
| felschr | Lily Foster, I guess buildNpmPackage could add a npmWorkspaces option to simplify building multiple workspaces. It's not really an issue, though, to just build the other packages in a preBuild. | 20:55:25 |
| felschr | Also, thank you for your help on that PR again. | 20:57:18 |
 Lily Foster | In reply to @felschr:matrix.org
Lily Foster, I guess buildNpmPackage could add a npmWorkspaces option to simplify building multiple workspaces. It's not really an issue, though, to just build the other packages in a preBuild. It's weird to understand what that would mean though. Like do they all just get installed side-by-side in $out/lib/node_modules and bins all installed in $out/bin? | 20:57:22 |
| felschr | hmm, right | 20:57:56 |
| Lily Foster | I guess that could make sense | 20:58:14 |
| felschr | something like npmWorkspaceDeps? | 20:58:17 |
| Lily Foster | really npm should be doing this correctly tbh | 20:58:39 |
| felschr | in my case I only need those package to be built so the main workspace can use them as dependencies | 20:58:46 |
| Lily Foster | Yeah | 20:58:58 |
| 19 Oct 2023 |
 Marie | this missing integrity hash bug in npm just got me again, are there currently plans to handle this? | 12:54:20 |
| Lily Foster | plans yes | 12:54:57 |
| Lily Foster | time, we'll see | 12:55:02 |
| Lily Foster | if someone wants to work on it, i can push my wip code to refactor lockfile fixup and provide guidance | 12:55:18 |
| Lily Foster | (pls i need more ppl on the nodejs team ðŸ˜) | 12:55:42 |
| Marie | In reply to @lily:lily.flowers
if someone wants to work on it, i can push my wip code to refactor lockfile fixup and provide guidance i could take a look at it | 12:56:38 |
| Lily Foster | In reply to @marie:marie.cologne
i could take a look at it i gotta deal with $dayjob rn, but i'll post stuff later if you wanna look | 12:57:37 |
| Lily Foster | thank youuuu (no pressure if you find it too much, but i appreciate even just more eyes on it) | 12:58:01 |
| 21 Oct 2023 |
| Marie | In reply to @lily:lily.flowers
i gotta deal with $dayjob rn, but i'll post stuff later if you wanna look meow | 12:08:00 |
| Lily Foster | In reply to @marie:marie.cologne
meow thank you for reminder, i,,, uh, forgot | 12:08:20 |
| Lily Foster | i'm on mobile but i'll post tonight (and am setting a reminder in my phone) when i'm at my laptop again | 12:08:37 |
| Marie | okay, no worries :3 | 12:08:55 |
|  @vid:matrix.org left the room. | 14:59:41 |
| 22 Oct 2023 |
|  daniel joined the room. | 13:57:02 |
| daniel | Hi! I'm experiencing some node-gyp errors when building a package with buildNpmPackage.
Specifically, I get the error npm ERR! gyp: binding.gyp not found (cwd: /build/1501d1ijr2j8h40cgy6b8wwaz88hi53l-source/node_modules/@maplibre/maplibre-gl-native) while trying to load binding.gyp. Is anyone familiar with a way to migitate this, or is it possibly an upstream issue?
| 14:01:56 |
 Cobalt | Anything node-gyp related tends to be a missing dependency. `maplibre-gl-native` sounds like something that needs OpenGL. | 14:04:42 |
| Cobalt | Have you checked if the package requires another native library? This dependency may need to be added to `buildInputs` (or other inputs, depending on the usage) | 14:05:54 |
| daniel | I get it working in my dev shell when running npm run build. I see that the maplibre-gl-native package doesn't bundle binding.gyp like usual, and uses node-pre-gyp instead to fetch it from GitHub. | 14:05:59 |
| Cobalt | Ah, nix build/ nix-build iirc don't allow direct internet access for npm. | 14:07:13 |
| Cobalt | In general it's not a good idea but you may be able to get around it by deactivating the sandbox for this specific build: `nix build --option sandbox=false ...`
See also this related discussion: https://discourse.nixos.org/t/how-do-i-access-internet-inside-nix-build/7671/2 | 14:13:28 |
