| 8 Jan 2025 |
otanaut | Hey, it's my first attempt at building a package using buildNpmPackage, and I noticed that the npm-packages of a child dependency of the project don't seem to be installed.
Parent package-lock.json references child-npm-dep which has a yarn.lock and the dependencies from yarn.lock are not available so the build fails. How could i resolve this?
Maybe its also a permission issue. Not sure. | 00:11:59 |
| magic_rb joined the room. | 00:13:02 |
otanaut | Ah it was/is a permission issue, i can resolve this by enabling makeCacheWritable but then i run into `pm error prebuild-install warn install getaddrinfo EAI_AGAIN github.com`
Seems the package tries to download prebuilt binaries. | 00:26:54 |
Emma [it/its] | sadly common, iirc you have to provide the built dependency itself through nix? | 03:49:14 |
Winter | correct | 03:59:50 |
otanaut | Is the correct approach to use node2nix then and overwrite the dependency? | 09:03:58 |
| 9 Jan 2025 |
otanaut | Could someone help how to add an override first locally for testing, and then later in nixpkgs, so that the package I am trying to add uses the pre-built node-gyp binary? | 20:51:50 |
Winter | what do you mean pre-built? from where? | 20:53:56 |
otanaut | This package https://github.com/koush/scrypted/blob/main/server/package.json#L7 uses node-gyp and when i run my buildNpmPackage derivation i run into a EAI_AGAIN error | 20:56:10 |
otanaut | I assume its because node tries to download a prebuild version of node-gyp which fails as the derivations do not have network access | 20:56:39 |
Winter | can you paste the full logs? | 20:58:04 |