| 25 Apr 2024 |
 Cobalt | In reply to @lily:lily.flowers
(can't promise help though because i'm bedridden recovering from surgery rn. maybe poke me about it like monday or tuesday?) Thank you for the offer, wishing you a restful recovery. | 18:00:55 |
| 26 Apr 2024 |
|  Qyriad changed their display name from Qyriad to Qyriad (she/they). | 23:47:44 |
| Qyriad changed their display name from Qyriad (she/they) to Qyriad. | 23:47:57 |
| 27 Apr 2024 |
| Qyriad changed their display name from Qyriad to Qyriad . | 00:01:06 |
| Qyriad changed their display name from Qyriad to Qyriad. | 00:09:42 |
| Cobalt | In reply to @c0ba1t:matrix.org
Hi, does someone know how get buildNpmPackage working with npm workspaces? It appears to not properly merge the node_modules from the workspace and the root, resulting in missing dependencies The problem appears to have been my installPhase, workspaces apparently have two node_modules directories and the one next to the package.json for the workspace also needs to be copied alongside the root node_modules. | 13:38:04 |
| Cobalt | In reply to @c0ba1t:matrix.org
Hi, does someone know how get buildNpmPackage working with npm workspaces? It appears to not properly merge the node_modules from the workspace and the root, resulting in missing dependencies * The problem appears to have been my installPhase, workspaces apparently have two node_modules directories and the one next to the package.json for the workspace also needs to be copied alongside the root node_modules.
It still doesn't run well but that's due to a bug in the code and not the nix derivation ;)
| 13:39:11 |
 Lily Foster | In reply to @c0ba1t:matrix.org
The problem appears to have been my installPhase, workspaces apparently have two node_modules directories and the one next to the package.json for the workspace also needs to be copied alongside the root node_modules. ohhhh yeah the default installPhase does do that part. i should have noticed that you'd overridden it | 14:55:51 |
| 29 Apr 2024 |
|  NixOS Moderation Botchanged room power levels. | 15:29:41 |
|  matejam joined the room. | 20:47:28 |
| matejam | Hello, I'm running npm ci in a fixed-output derivation and I'm getting an UNABLE_TO_GET_ISSUER_CERT_LOCALLY error from npm. Any ideas how can I fix this? | 21:36:46 |
| 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 |
| matejam |
oh you're not using buildNpmPackage. yeah you'll want something like that
I'm not using buildNpmPackage because I'm also calling php's composer and I don't know how to combine different builders...
| 22:24:45 |
| matejam | *
oh you're not using buildNpmPackage. yeah you'll want something like that
I'm not using buildNpmPackage because I'm also calling php's composer and I don't know how to combine different builders...
| 22:24:55 |
| Lily Foster | In reply to @matejam:matrix.org
oh you're not using buildNpmPackage. yeah you'll want something like that
I'm not using buildNpmPackage because I'm also calling php's composer and I don't know how to combine different builders...
you can do a postBuild script, or you can mix and match build hooks (idk how to deal with composer) | 22:25:26 |
| Lily Foster | (but you don't have to use either if you don't want to (assuming FOD unreproducibility isn't a problem for what you're doing)) | 22:26:20 |
| Lily Foster | In reply to @samasaur:matrix.org
If you're in a fixed-output derivation, you have internet access. I think you need to add cacert to nativeBuildInputs (and yes, this is probably the immediate cause of the error) | 22:26:36 |
| matejam | In reply to @samasaur:matrix.org
If you're in a fixed-output derivation, you have internet access. I think you need to add cacert to nativeBuildInputs That does something, now I have a different error message 😄
EACCES: permission denied, mkdir '/homeless-shelter' | 22:27:03 |
| Lily Foster | In reply to @matejam:matrix.org
That does something, now I have a different error message 😄
EACCES: permission denied, mkdir '/homeless-shelter' yeahh it's gonna be a lot of things like that which the npm hooks already handle (there's, uh, a lot of edge cases) | 22:27:44 |
| samasaur | https://github.com/NixOS/nix/issues/670#issuecomment-1211700127 | 22:28:33 |
| samasaur | looks like this linked comment should solve your issue | 22:28:42 |
| samasaur | at the start of buildPhase, run export HOME=$(pwd) | 22:29:07 |
| samasaur | but lily is correct that we're really re-solving problems that the npm hooks have already solved | 22:29:46 |
