In reply to @lily:lily.flowers
If you're trying to get something specific working, there is a yarn v2+ to yarn v1 lockfile rewriter in nixpkgs that some packages have used

I thought it was. I may be misremembering?

(If it is though, it might be easier if yarn berry turns out to be a lot of trouble to create new tooling for atm)

  offlineCache = stdenvNoCC.mkDerivation {
    name = "cal.com-${version}-offline-cache";

    inherit src;

    nativeBuildInputs = [ yarn ];

    HOME = "/build";
    buildPhase = ''
      yarn config set enableTelemetry 0
      yarn config set cacheFolder $out
      yarn
    '';

    outputHashAlgo = "sha256";
    outputHashMode = "recursive";
    outputHash = "sha256-w/nwiMntMsi+G55iZF9QwdA7ZFe/XOtA19AUqboLFWA=";
  };

In reply to @janne.hess:helsinki-systems.de
(we will see if this also builds in a couple of months…)

In reply to @lily:lily.flowers
Wait this would still be yarn v1 right? We don't have yarn-berry in nixpkgs yet I thought

In reply to @lily:lily.flowers
Wait this would still be yarn v1 right? We don't have yarn-berry in nixpkgs yet I thought

yarn set version 3.4.1

In reply to @adam:valkor.net
mkYarnPackage reads the package.json from src. This should work as expected right? in https://github.com/NixOS/nixpkgs/pull/241314 the submitter is saying they're receiving this error when trying to build without copying package.json into nixpkgs: https://gist.github.com/GrahamcOfBorg/77965b591af2aef7b6a5c40bb0d08391

In reply to @lily:lily.flowers
You also need the yarn.lock and yarn.nix... it's, uh, unfortunate

In reply to @adam:valkor.net
i was looking at pnpm-lock-export yesterday to see if i could add the newer lock file format. so you're telling me we probably don't want to go pnpm->yarn :)

In reply to @lily:lily.flowers
Well I hope to dump yarn2nix at some point. We're cooking up newer tooling for yarn but it'll be a bit