!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

209 Members
59 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
3 Jul 2023
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.de
In reply to @lily:lily.flowers
I intend to, it's on the todo list. Not much yet though
Doesn't work with fetchYarnDeps either I guess? :/
16:56:34
@lily:lily.flowersLily Foster
In reply to @janne.hess:helsinki-systems.de
Doesn't work with fetchYarnDeps either I guess? :/
It will only work with that when I get to it. Yarn2nix makes me sad
16:59:09
4 Jul 2023
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.deOkay I tried and I gotta say: yarn is the absolute worst08:38:33
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.deParsing the lock is actually very easy, resolving the resolution to a usable URL is absolutely not08:42:08
@lily:lily.flowersLily Foster
In reply to @janne.hess:helsinki-systems.de
Okay I tried and I gotta say: yarn is the absolute worst
Idk, npm is pretty bad. At least yarn isn't quite so happy to silently ignore errors and redownload a bunch of stuff when you breath on it wrong
08:42:10
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.de
In reply to @lily:lily.flowers
Idk, npm is pretty bad. At least yarn isn't quite so happy to silently ignore errors and redownload a bunch of stuff when you breath on it wrong
I was talking about the code, not the actual use ;)
08:42:31
@lily:lily.flowersLily Foster* Idk, npm is pretty bad. At least yarn isn't quite so happy to silently ignore errors and redownload a bunch of stuff when you breathe on it wrong08:42:34
@lily:lily.flowersLily Foster
In reply to @janne.hess:helsinki-systems.de
I was talking about the code, not the actual use ;)
Fair
08:42:39
@lily:lily.flowersLily FosterThe yarn lockfile format is custom cancer08:42:54
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.dethe v2 is a lot better, that's proper yaml08:43:04
@lily:lily.flowersLily Foster
In reply to @janne.hess:helsinki-systems.de
Parsing the lock is actually very easy, resolving the resolution to a usable URL is absolutely not
Also this
08:43:06
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.debut it doesn't have a URL08:43:09
@lily:lily.flowersLily FosterOh really 💀08:43:20
@lily:lily.flowersLily FosterI hadn't looked at the yarn-berry stuff yet. It's just been on my todo list08:43:37
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.de
In reply to @janne.hess:helsinki-systems.de
but it doesn't have a URL

reference: 'npm:2.0.4'

08:44:39
@lily:lily.flowersLily FosterI more or less expect to get to it after the current in-progress PRs are dealt with on the node project board on github, and after npmCheckHook and buildYarnPackage are merged too08:45:30
@lily:lily.flowersLily Foster
In reply to @janne.hess:helsinki-systems.de

reference: 'npm:2.0.4'

Yeah, was worried they'd have done that. The references are unfortunate because they're entirely dependent on the locally configured registry (reminds me of another registry we have.... ❄)
08:46:36
@lily:lily.flowersLily Foster
In reply to @janne.hess:helsinki-systems.de

reference: 'npm:2.0.4'

They still have integrity hashes at least, right?
08:47:30
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.de

Say - instead of parsing the lock, couldn't I just:

echo 'yarn-offline-mirror "./yarn-offline-mirror"' >> .yarn.conf
yarn install
nix-store --add ./yarn-offline-mirror

or something like this?

08:47:42

Show newer messages


Back to Room ListRoom Version: 6