Nix NodeJS | 194 Members | |
| 56 Servers |
| Sender | Message | Time |
|---|---|---|
| 17 Apr 2024 | ||
| 05:34:06 | ||
| 25 Apr 2024 | ||
| 03:36:37 | ||
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 | 16:00:26 | |
In reply to @c0ba1t:matrix.orgit does handle them (assuming they are npm workspaces and not the fake ones lerna and such mash together) | 16:17:37 | |
| can you share derivation? | 16:17:41 | |
In reply to @lily:lily.flowershttps://git.tu-berlin.de/proveit/proveit.nix/-/blob/main/pkgs/proofbuddy.nix?ref_type=heads#L89 | 16:20:59 | |
| I can also share the package.json files but the source code is unfortunately not public | 16:21:18 | |
| yes, please share the package.json of the root workspace dir, of the workspace package, and the package-lock.json of the root workspace dir | 16:22:00 | |
| (you can DM if you prefer) | 16:22:08 | |
| (can't promise help though because i'm bedridden recovering from surgery rn. maybe poke me about it like monday or tuesday?) | 16:22:36 | |
In reply to @c0ba1t:matrix.org(yeah i'm trying to look at derivation but i'm wayy too incoherent rn...) | 16:23:17 | |
In reply to @lily:lily.flowersThank you for the offer, wishing you a restful recovery. | 18:00:55 | |
| 26 Apr 2024 | ||
| 23:47:44 | ||
| 23:47:57 | ||
| 27 Apr 2024 | ||
| 00:01:06 | ||
| 00:09:42 | ||
In reply to @c0ba1t:matrix.orgThe 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 | |
In reply to @c0ba1t:matrix.org* The problem appears to have been my It still doesn't run well but that's due to a bug in the code and not the nix derivation ;) | 13:39:11 | |
In reply to @c0ba1t:matrix.orgohhhh yeah the default installPhase does do that part. i should have noticed that you'd overridden it | 14:55:51 | |
| 29 Apr 2024 | ||
| 15:29:41 | ||
| 20:47:28 | ||
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 | |
| 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 | |
| If possible, please share your derivation to make it easier for us to try to help you. | 22:17:41 | |
| 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 | |
| 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 | |
| npmConfigHook does the npm ci for you | 22:22:14 | |
| oh you're not using buildNpmPackage. yeah you'll want something like that | 22:22:57 | |
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 | |
If you're in a fixed-output derivation, you have internet access. I think you need to add cacert to nativeBuildInputs | 22:23:54 | |