Oleg Lebedev

The only one aspect of `flake.{nix,lock}` + `flake-compat` usage I haven't thought about before is the ability to define the dependencies at the call site. The idea of flakes is...

It removes the `__functor` property here https://github.com/edolstra/flake-compat/blob/master/default.nix#L193. I am wondering, would it work if we just do `pkgs.callPackage ./default.nix` from `flake.nix`? This should remove the divergence problem and make flake...

Hi @yangm97, Yeah, this is a known issue with the current approach. I agree that it's far from perfect and adds maintainability burden which we better to avoid. As long...

> I wonder if it would be possible to pay the IFD cost during the yarn.lock.nix generation instead of per package. Ah, I see, we can introduce a flag to...

> On a side note, I noticed there's a circular dependency cycle going on with babel/core and babel/whatever-transforms, so if I try to override babel/core into this dependency I get...

Oh, yes, this doesn't look neat, 100%. Yeah, I guess, you would need to modify this section [here](https://github.com/canva-public/js2nix/blob/main/lib/print.js#L466-L493) in the way it asynchronously fetch `N` packages in parallel and build...

As a workaround for the projects that face this check issue: ```nix let env = pkgs.js2nix { package-json = ./package.json; yarn-lock = ./yarn.lock; overlays = [ (self: super: { #...

Looks like a incompatibility issue between lock file formats. I see you use Yarn v3, I haven't tested the `js2nix` against the newer versions of the lock file that the...

Hi @bouk, wow, it looks awesome! 🙂 > so it can work without having to generate and commit a `yarn.lock.nix` file. This would make the user experience a lot nicer...

> The readFile would cause an IFD if the yarn.lock file was generated as well, so if you're packaging up your own code that should be fine. Oh, you are...