@microsoft/just could provide a known issue and/or a warning if another cli has been detected in $PATH.

[peterkc]

casey/just has been using the the cli name just since 11/2017. Perhaps consider using just-cli instead to avoid the conflict?

[kenotron]

oh interesting - do you mean npx just would cause an issue here?

[peterkc]

@kenotron

Given:

• casey/just is installed to /usr/local/bin/just
• @microsoft/just is install and available at ./node_modules/.bin/just

@microsoft/just will have a higher priority over /usr/local/bin/just for npm run and npx just.

If a project is using a Justfile, then /usr/local/bin/just will not work.

To resolve the conflicts and have both cli coexists, users would have the following options.

"scripts": {
  "use-ms-just-option-1": "npx just task-name",
  "use-ms-just-option-2": "./node_modules/.bin/just task-name",
  "use-casey-just-option-1": "/usr/local/bin/just task-name",
  "use-casey-just-option-2": "just-alias task-name",
  "use-casey-just-option-3": "./Justfile task-name",
},

For @microsoft/just:

• use npx just
• ./node_modules/.bin/just

For casey/just:

• use absolute path
• create a symlink _just -> /usr/local/bin/just
• a shebang in Justfile (i.e. #!/usr/bin/env just --justfile)

@microsoft/just could provide a known issue and/or a warning if another cli has been detected in $PATH.

[kenotron]

@microsoft/just could provide a known issue and/or a warning if another cli has been detected in $PATH.

Oh that's an interesting feature... I'm going to rename this issue so to reflect this idea.

[github-actions[bot]]

Issues seem to have gone stale.