This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/vercel/turbo-site/5e8hrGBitVJG4rU1cN8VVZGVJhCW
✅ Preview: https://turbo-site-git-fork-xenfo-feat-lockfile-context-logic.vercel.sh

So my thinking is that each backend should be responsible / have a function for resolving a given package's external dependencies (out of the backend's lockfile) in an abstracted manner so that the implementation details of the backend leaked into context.go.

I'm a bit confused with what you want. I have it so that it goes through the keys each backend provides (only yarn and yarn berry is supported so the other backends have empty arrays) and gets the lockfile entry. Do you want it to resolve the entry in the backend and not in context?

I'm a bit confused with what you want. I have it so that it goes through the keys each backend provides (only yarn and yarn berry is supported so the other backends have empty arrays) and gets the lockfile entry. Do you want it to resolve the entry in the backend and not in context?

@jaredpalmer I need further guidance on this.

@xenfo IIUC, the idea would be to remove usages of util.IsYarn from context.go and instead have the relevant functionality baked into the backend.

@xenfo is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

Are you still working on this?

Yeah I'll try to finish it this weekend.

@jaredpalmer I took a look, and I'm not sure how to move it, some things are context specific.