Allow builds without dream.lock

[wmertens]

I don't quite understand the whole system yet, but it occurred to me that with #195 the translate step is entirely stateless if the package-lock.json file is v2.

So it would be nice to not have to maintain a separate dream-lock file in git.

How about providing the minimum information in flake.nix (I believe just the package names?), and then running a stateless translate step before the build?

Then direnv could be told to watch package-lock.json and when it changes, update the devShell, no resolveImpure step needed.

[DavHau]

The way you describe it is how it works already. There exist pure and impure translators in dream2nix. If your project can be translated by a pure translator, which is the case if you have either a package-lock.json or yarn.lock file there is no need to execute resovleImpure. resolveImpure is only needed if a lock file is not present.

[wmertens]

Hmm, but without resolveImpure you don't have devShell?

[DavHau]

Hmm, but without resolveImpure you don't have devShell?

If that is the case, than this is a bug that needs to be fixed

[DavHau]

I just tested and I get the devShell outputs also without resolveImpure. If you have a project where this is not the case, please file an issue providing a flake.