Nix NodeJS | 209 Members | |
| 60 Servers |
| Sender | Message | Time |
|---|---|---|
| 18 Feb 2023 | ||
| not atm unless you use node2nix | 16:58:56 | |
In reply to @winterqt:nixos.devBut that would only read package.json, not yarn.lock? | 16:59:48 | |
| you can nuke the yarn.lock and generate a lockfile from that | 17:00:52 | |
*npm lockfile with npm install | 17:01:04 | |
| by that point you can just use fetchNpmDeps though that lockfile size may be huge ugh | 17:01:25 | |
| Has anyone tried using https://github.com/imsnif/synp ? I wonder if it's deterministic | 17:01:25 | |
| Oh, same issue though: https://github.com/imsnif/synp/issues/95 | 17:02:03 | |
| it requires an already populated node_modules tree :/ | 17:02:13 | |
| and probably doesn't support v3 | 17:02:20 | |
| * and probably doesn't support v2 | 17:02:23 | |
| Well, no build from source then. | 17:03:58 | |
In reply to @winterqt:nixos.devWe have the yarn fetcher, so they can use that, right? | 17:07:20 | |
| not with v2 | 17:08:42 | |
| v2 what? | 17:09:10 | |
| yarn | 17:09:28 | |
| entirely different lockfile format | 17:09:33 | |
| Ohhh right forgot about that | 17:09:45 | |
In reply to @lily:lily.flowershttps://github.com/yarnpkg/berry | 17:09:51 | |
In reply to @robert:funklause.deYeah I knew about it but have mostly tried to ignore its existence. We don't have tooling for it so something like node2nix (that locks in Nix code rather than yarn.lock) might be one of the only solutions | 17:11:05 | |
| 1 Mar 2023 | ||
How can we make the npmInstallHook work with workspaces? https://github.com/NixOS/nixpkgs/pull/218923 | 03:18:59 | |
In reply to @robert:funklause.deI planned to dig in to npm at some point to figure out why it is convinced it still needs to get dep metadata from the internet when the entire lockfile is cached. Because as far as I remember, it should otherwise theoretically work. Alternatively if all of the packages are in the npm registry you could just fetch from there and it doesn't have that problem | 11:37:24 | |
| 6 Mar 2023 | ||
| 11:52:49 | ||
| 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 | |