The idea here is to make yarn2nix (the program) emit pure data instead of code, and then interpret that on the Nix side. For the case of tarring up git dependencies, it means not having to embed the tar call in the generated file. It also allows custom fetchers which can embed authentication for access to private registries.
While I'm here, remove instances of % in names. I observed this in a url escaped slash (%2f).
This is is a breaking change to the generated dependency file format. All consumers will have to regenerate their yarn.nix files.
The idea here is to make
yarn2nix
(the program) emit pure data instead of code, and then interpret that on the Nix side. For the case of tarring up git dependencies, it means not having to embed the tar call in the generated file. It also allows custom fetchers which can embed authentication for access to private registries.While I'm here, remove instances of
%
in names. I observed this in a url escaped slash (%2f
).This is is a breaking change to the generated dependency file format. All consumers will have to regenerate their yarn.nix files.