| 17 May 2023 |
 Lily 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 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 Foster | So this lockfile needs to be deleted and regenerated | 22:12:24 |
| Lily Foster | https://github.com/bokeh/bokeh/blob/branch-3.2/bokehjs/package-lock.json#L101-L114 | 22:12:31 |
 hexa | (django-hijack is finished btw :)) | 22:12:38 |
| hexa | rough, not going to commit a 143 kB lock file into nixpkgs ;D | 22:12:56 |
| hexa | * rough, not going to commit a 143 kB lock file into nixpkgs 😄 | 22:12:58 |
| Lily Foster | npm still will not do automatic fixup of this issue: https://github.com/npm/cli/issues/4460 | 22:13:13 |
| Lily Foster | Which is dumb | 22:13:20 |
| Lily 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 | alright | 22:16:41 |
| Lily 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 |
| hexa |
npm install --package-lock
| 22:17:44 |
| Lily Foster | npm is pretty hecked | 22:17:48 |
| hexa | that did nothing to the lock file | 22:18:02 |
