| 29 Apr 2024 |
 Cobalt | Otoh you might likely lack some ca certificates. However, how to fix that depends on where (env, phase) you exactly call `npm ci`. | 22:16:38 |
| Cobalt | If possible, please share your derivation to make it easier for us to try to help you. | 22:17:41 |
 matejam | I'm calling it in the build phase. Here's my derivation: https://github.com/MatejaMaric/yota-laravel/blob/8216bcd18ac36805a0d1dc1eb08ebc7fa05f6bfe/derivation.nix | 22:19:23 |
| Cobalt | I don't think you have internet access in the build phase. That should make an `npm ci` call unlikely to work and would also explain why no ca certificates are present. | 22:21:19 |
 Lily Foster | npmConfigHook does the npm ci for you | 22:22:14 |
| Lily Foster | oh you're not using buildNpmPackage. yeah you'll want something like that | 22:22:57 |
| matejam | I quite sure fixed-output (outputHash ) of my derivation solves that problem. In the derivation code you can see that I'm calling composer install which also requires internet access. | 22:23:24 |
 samasaur | If you're in a fixed-output derivation, you have internet access. I think you need to add cacert to nativeBuildInputs | 22:23:54 |
