feature request: add support for devenv

[y-cg]

Hi! Thanks for building such a useful tool! Are you planning to add support for devenv?

I haven't had a chance to dig into the codebase yet, but I imagine a straightforward implementation could simply allow users to specify the lock file path. devenv uses devenv.lock, which — unless I'm missing something — shares the same format as flake.lock.

[samestep]

Sure, I can take a look! I've never used devenv before, so I'll need your help testing (or writing? 👀) such a PR to ensure it works for your use case.

Question: I see that devenv 2.0 was just released, does this introduce any backward incompatibilitities that I'd need to account for?

[samestep]

Another question: when you say "support for devenv", I could imagine one of two things:

1. An alternate installation method for npc via devenv instead of using nix shell or a flake input
2. The ability for npc log, npc checkout, and npc bisect to read and write devenv.lock instead of just flake.lock

At first I assumed you only meant the second one; is that accurate?

[y-cg]

so I'll need your help testing (or writing? 👀)

Sure, I'd love to help! I do have some experience with Rust, so feel free to ping me anytime. :)

Question: I see that devenv 2.0 was just released, does this introduce any backward incompatibilitities that I'd need to account for?

I've been testing on the new release as well and haven't run into any backward incompatibilities so far (at least within the scope of devenv.lock). That said, I'd recommend pinning devenv to v1.11.2, or v2.0.3 if you'd prefer to stay on the latest — the first couple of 2.0.x releases had some quirks.

At first I assumed you only meant the second one; is that accurate?

Yes, the second approach should be sufficient on its own — no need to introduce a new binary. Also, just a small hint: devenv defines inputs in devenv.yaml, not devenv.nix.