!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

198 Members
58 Servers

Load older messages


SenderMessageTime
17 May 2023
@hexa:lossy.networkhexa😄21:45:38
@lily:lily.flowersLily Foster Oh. The prePatch 21:46:05
@hexa:lossy.networkhexanpmRoot fix when 😄21:46:21
@hexa:lossy.networkhexafixes the build, breaks the update workflow 😫21:46:39
@lily:lily.flowersLily Foster Well when npmRoot is working, it should fix the update script, right? 21:47:03
@hexa:lossy.networkhexaI would think so21:47:09
@lily:lily.flowersLily FosterOkay, wasn't sure if I was misunderstanding21:47:17
@hexa:lossy.networkhexaI have evcc which is basically doing the same, but without the need for npmRoot21:47:25
@hexa:lossy.networkhexawould be great to sort this out before the release, because I did in fact tell people about buildNpmPackage, when I asked them to migrate off of node 14/16 🙂21:48:51
@lily:lily.flowersLily FosterI do fully intend to have these sorts of things fixed asap, since we're coming up so close on release and with the node 14/16 stuff21:49:45
@lily:lily.flowersLily FosterSo I'm thinking npm is ignoring the cache because it's may ending up in this code path, which throws an error without logging and that error gets silently caught (thanks npm, real cool): https://github.com/npm/pacote/blob/3307ad9c1600b6a60b2250c2239240ac41fc7b07/lib/fetcher.js#L31721:53:06
@lily:lily.flowersLily Foster * So I'm thinking npm is ignoring the cache because it's maybe ending up in this code path, which throws an error without logging and that error gets silently caught (thanks npm, real cool): https://github.com/npm/pacote/blob/3307ad9c1600b6a60b2250c2239240ac41fc7b07/lib/fetcher.js#L31721:53:13
@lily:lily.flowersLily Foster Time to add some debug logging and figure out what that cacache function is getting called with... hopefully it's not a bug, but npm having a ton of silently broken things because of their silently-bail-out-and-refetch logic all over the place is not news 21:55:58
@lily:lily.flowersLily Foster (like their hosted tarball url thing for gitlab is just straight up wrong and they have no intentions to fix it -- so when you do gitlab: deps they're unnecessarily way slower than any other hosted git provider because it tries the tarball, fails, and falls back to checkouts through complicated spaghetti code paths) 21:57:00
@lily:lily.flowersLily Foster(so it's "not a problem" because it handles it I guess)21:57:21
@hexa:lossy.networkhexayikes 😄22:02:00
@hexa:lossy.networkhexahttps://github.com/bokeh/bokeh/blob/branch-3.2/bokehjs/package.json#L29-L3222:10:50
@hexa:lossy.networkhexaI'm not quite sure which of these workspaces is the interesting one22:11:04
@lily:lily.flowersLily Foster Okay. So. This isn't actually an issue with workspaces. I looked in the lockfile to make sure it existed with more than nothing in it. But I must be tired because while it's present, it's actually just missing integrity and resolved fields 22:11:19
@lily:lily.flowersLily Foster * Okay. So. This isn't actually an issue with workspaces. I looked in the lockfile to make sure the p-map dep existed with more than nothing in it. But I must be tired because while it's present, it's actually just missing integrity and resolved fields 22:11:31
@lily:lily.flowersLily FosterSo this lockfile needs to be deleted and regenerated22:12:24
@lily:lily.flowersLily Fosterhttps://github.com/bokeh/bokeh/blob/branch-3.2/bokehjs/package-lock.json#L101-L11422:12:31
@hexa:lossy.networkhexa(django-hijack is finished btw :))22:12:38
@hexa:lossy.networkhexarough, not going to commit a 143 kB lock file into nixpkgs ;D22:12:56
@hexa:lossy.networkhexa * rough, not going to commit a 143 kB lock file into nixpkgs 😄22:12:58
@lily:lily.flowersLily Fosternpm still will not do automatic fixup of this issue: https://github.com/npm/cli/issues/446022:13:13
@lily:lily.flowersLily FosterWhich is dumb22:13:20
@lily:lily.flowersLily Foster
In reply to @hexa:lossy.network
rough, not going to commit a 143 kB lock file into nixpkgs 😄
Yeah the lockfile committing to nixpkgs across multiple ecosystems has been a bit unfortunate (the node2nix node-packages.nix files included)... You could submit a PR to fix the lockfile and fetchpatch the PR if you are so inclined, to avoid that
22:16:28
@hexa:lossy.networkhexaalright22:16:41
@lily:lily.flowersLily Foster But there's no reproducible way to handle that as-is. Except maybe doing something like how importCargoLock handles git deps with the extra hashes and hope and pray the version exists in the registry 22:17:29

There are no newer messages yet.


Back to Room ListRoom Version: 6