| 3 Jan 2024 |
 Lily Foster | it's not actually using npm, right? | 13:41:07 |
 @janne.hess:helsinki-systems.de | I hope not | 13:41:22 |
| Lily Foster | and you do need nodedir too | 13:41:31 |
| @janne.hess:helsinki-systems.de | I had another package recently that needed yarn, npm and node | 13:41:34 |
| Lily Foster | In reply to @janne.hess:helsinki-systems.de
I hope not (that var just activates a sleeper agent we installed in npm to fix some of its broken behavior and inject vars when their fetcher lib re-execs the entirety of npm for git deps........) | 13:42:17 |
| Lily Foster | In reply to @lily:lily.flowers
(that var just activates a sleeper agent we installed in npm to fix some of its broken behavior and inject vars when their fetcher lib re-execs the entirety of npm for git deps........) (their coherence model for the moving parts of npm is utterly hecked) | 13:42:51 |
| @janne.hess:helsinki-systems.de | TIL about srcOnly | 13:44:27 |
| @janne.hess:helsinki-systems.de | In reply to @lily:lily.flowers
(that var just activates a sleeper agent we installed in npm to fix some of its broken behavior and inject vars when their fetcher lib re-execs the entirety of npm for git deps........) obviously :D | 13:44:47 |
| Lily Foster | In reply to @lily:lily.flowers
(that var just activates a sleeper agent we installed in npm to fix some of its broken behavior and inject vars when their fetcher lib re-execs the entirety of npm for git deps........) (and it re-execs npm without necessarily even ensuring lockfiles are coherent in the git dep and requiring them since it doesn't lock those needed deps in the original lockfile. and npm loves to silently get spooked, ignore the lockfile, and try to redownload literally everything..........) | 13:45:32 |
| Lily Foster | (oh and don't forget it drops the passed options when it re-execs. i mean come on, who needs those?) | 13:46:18 |
| Lily Foster | (at least they set an env var to ensure they don't accidentally recurisvely re-exec npm with no end, right?) | 13:46:39 |
| Lily Foster | (ugh npm makes me sad) | 13:46:44 |
| Lily Foster | (sorry for rant...) | 13:46:50 |
| @janne.hess:helsinki-systems.de | In reply to @lily:lily.flowers
(ugh npm makes me sad) try yarn, might make you sadder | 13:47:30 |
| Lily Foster | In reply to @janne.hess:helsinki-systems.de
try yarn, might make you sadder i doubt that tbh. sure it's missing some stuff we want for reproducibility, but at least it felt somewhat more intelligently designed | 13:48:04 |
| @janne.hess:helsinki-systems.de | In reply to @lily:lily.flowers
i doubt that tbh. sure it's missing some stuff we want for reproducibility, but at least it felt somewhat more intelligently designed
➤ 8;;https://yarnpkg.com/advanced/error-codes#yn0060---incompatible_peer_dependencyYN00608;;: │ vitest@npm:0.34.6 [f9b2d] provides @types/node (pe6001) with version 16.9.1, which doesn't satisfy what vite requests
| 13:48:19 |
| Lily Foster | and their solution to lockfile reproducibility involves actually sane locking that doesn't produce megabytes large dep trees | 13:48:26 |
| @janne.hess:helsinki-systems.de | In reply to @janne.hess:helsinki-systems.de
➤ 8;;https://yarnpkg.com/advanced/error-codes#yn0060---incompatible_peer_dependencyYN00608;;: │ vitest@npm:0.34.6 [f9b2d] provides @types/node (pe6001) with version 16.9.1, which doesn't satisfy what vite requests
(not an error btw because I ran yarn dedupe first) | 13:48:49 |
