In reply to @janne.hess:helsinki-systems.de
There is a checksum field which looks like a sha512 hash

In reply to @lily:lily.flowers
Is it sri or just bare sha512?

checksum: d415fb2f063a024e2d382e8dc5e66929d0d9bf94f2c22e03cde201dc2fa03e15d21274dbe5c23a26ce016a4cac3db93ad99fb454de76fd94bc1600fd7062eebe

In reply to @lily:lily.flowers
Possibly. The thing is I know they removed --offline with v2 so we gotta make sure we can still prevent it from needing anything online

In reply to @janne.hess:helsinki-systems.de
I will try. 5 lines of bash is probably a lot easier than having custom node code that parses 2 different lock files ;)

In reply to @lily:lily.flowers
Oh you mean for fetching. I'm not sure if lockfile fixup is still required for git deps for yarn berry or not. It was for yarn1 and so needed a custom fetcher

In reply to @janne.hess:helsinki-systems.de
No I mean for generating the hash for fetchYarnDeps

In reply to @janne.hess:helsinki-systems.de
No I mean for generating the hash for fetchYarnDeps

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