[Feature Request] Check version between ./node_modules and standalone binary

[awildeep]

Description

Recently I upgraded from 0.4.x to 0.6.3 of Varlock and I use the 1password plugin. Post upgrade I was getting an error nearly identical to #442.

What happened:

• I had installed Varlock via the standalone as 0.4.x, and in my project as 0.6.3. Then when I tried to execute code, I was apparently using the binary sometimes, and the version installed in my project other times, resulting as a issue like the one ticketed above.

Motivation

Reduce troubleshooting on end users. I was able to figure out my version disparity eventually, but the errors were misleading.

Proposed Solution

I am not sure of a great way to fix this issue, as I use Varlock inside my TypeScript project, and I am also using it for other languages. If we could get a check to see if running standalone; if the current path has Varlock installed, and if the versions match maybe?

Alternatives

No response

Additional Information

No response

[philmillman]

So if you're running a command from the standalone but we detect that it's in a folder with varlock already installed in node_modules is the expectation that it would yell at you and tell you to use the installed version?

Sorry for the pain, it's definitely a challenging problem, given that standalone and repo versions (including their plugins) could be different, etc

[awildeep]

So if you're running a command from the standalone but we detect that it's in a folder with varlock already installed in node_modules is the expectation that it would yell at you and tell you to use the installed version?

Sorry for the pain, it's definitely a challenging problem, given that standalone and repo versions (including their plugins) could be different, etc

I don't think I have the best suggestion to resolve the pain point (also no need to apologize, I love this project). My goal is to try and help users understand why something is broken like in the case I outlined above. Having to remember that my standalone and repo version could be desynced, it a little painful. Or maybe a warning if you use the standalone in a repo that has it installed?

I am not sure what is even potentially possible on this front, I am mostly trying to highlight the pain point I felt for two reasons:

1. Maybe it helps someone else if they stumble on this issue
2. Maybe a more elegant solution come out of this

[theoephraim]

If we see we are running via the standalone binary and that we are within a directory with node_modules and it's installed we can either defer to the installed version (with a warning?) or just fail with an error and tell you to use the installed one?

I wonder what other tools do - must be a few that are common to install both globally and within a project

[awildeep]

My personal take would be:

• if using the node_modules, no real checks need to be fired
• If using standalone, and there is a node_modules installed; having a warning to tell me I have a version match issue might have lead me to a fix faster

But this is just my best guess as to a good workflow, I am open to other or better solutions.

[awildeep]

@theoephraim thanks for update!