Nix NodeJS | 208 Members | |
| 58 Servers |
| Sender | Message | Time |
|---|---|---|
| 9 Mar 2023 | ||
| 03:25:04 | ||
| 10 Mar 2023 | ||
| I have a js package which is fighting me every step of the way here: https://github.com/dali99/nixpkgs/commit/79b02a249d096a20f7c0e9984ffb58cac6dde9f2 With downgrading to node 16 and running node-gyp in the package config there, some compilation happens, but when I run it I get
So it seems it's not linking libcds properly? Any ideas on what's going on here? | 06:14:34 | |
| * I have a js package which is fighting me every step of the way here: https://github.com/dali99/nixpkgs/commit/79b02a249d096a20f7c0e9984ffb58cac6dde9f2 With downgrading to node 16 and running node-gyp in the package config there, some compilation happens, but when I run it I get
So it seems it's not linking libcds properly? Any ideas on what's going on? | 06:14:42 | |
In reply to @dandellion:dodsorf.asHow are you running it? I can get --help output just fine from building your branch | 18:07:40 | |
| yeah, it's only when trying it a hdt datasource (which is the recommended datasource):
Like this config ^ | 18:31:26 | |
| Ah, I guess I could try to test that. What is libcds though? Is that part of the package? | 18:32:09 | |
| It's some datastructure library that seems to be shipped with https://github.com/RubenVerborgh/HDT-Node | 18:32:58 | |
| in the deps submodule | 18:33:07 | |
| 13 Mar 2023 | ||
anyone has come into similar problem ? :An unexpected error occurred: "ENOENT: no such file or directory, open '/homeless-shelter/.yarnrc'". | 20:59:53 | |
| https://0x0.st/HiFd.nix | 21:00:30 | |
needed to add export HOME=$(mktemp -d) | 21:10:44 | |
| 21 Mar 2023 | ||
| 20:43:25 | ||
| 24 Mar 2023 | ||
| Has anyone ever tried packaging an electron-forge app in Nixpkgs? | 00:11:51 | |
| There seems no way around electron-forge downloading the electron binary. If someone knows one please tell me | 02:11:09 | |
| 25 Mar 2023 | ||
I have a package that converted from yarn.lock to pnpm-lock.yaml | 11:34:12 | |
| I don't have any experience with the latter, what's the usual way of packaging those in nixpkgs | 11:34:39 | |
| A 2 seconds search lead me to: https://github.com/cvent/pnpm-lock-export | 11:34:56 | |
Which isn't packaged in nixpkgs... and also uses pnpm-lock.yaml | 11:35:17 | |
| * A 2 seconds search led me to: https://github.com/cvent/pnpm-lock-export | 11:37:51 | |
In reply to @ambroisie:belanyi.frIs it in npm registry? | 12:47:51 | |
| The registry tarball will have a package-lock.json if so | 12:48:05 | |
| No idea, I don't know the JS ecosystem funnily enough | 12:48:16 | |
| My only experience is packaging some front-ends for nixpkgs :') | 12:48:29 | |
| Wish I didn't know JS sometimes 🫠| 12:51:16 | |
| Seems to be on npmjs.com | 12:51:58 | |
Yep it is. So use fetchzip and https://registry.npmjs.org/pnpm-lock-export/-/pnpm-lock-export-${version}.tgz | 12:52:35 | |
| With buildNpmPackage | 12:52:45 | |
| And you should be good | 12:52:51 | |
| Thanks | 12:52:54 | |
Arf, no package-lock.json in the registry tarball | 13:00:09 | |