Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NVM + yarn global add @vue-storefront/cli@next doesn't expose "vsf" binary #4866

Closed
2 of 4 tasks
sudo-at-night opened this issue Sep 15, 2020 · 2 comments
Closed
2 of 4 tasks
Assignees
Labels
bug Bug reports

Comments

@sudo-at-night
Copy link
Contributor

Current behavior

  1. Install yarn global add @vue-storefront/cli@next
  2. Run vsf
  3. Results in Command 'vsf' not found, did you mean: [...]

Expected behavior

  1. Install yarn global add @vue-storefront/cli@next
  2. Run vsf
  3. Results in ERROR VSF Provide command

Steps to reproduce the issue

Steps described above in Current behavior and Expected behavior sections

Version of Vue Storefront

  • Vue Storefront
  • Vue Storefront Next

Can you handle fixing this bug by yourself?

  • YES
  • NO

Environment details

  • OS: Ubuntu 18.04
  • Node: v14.5.0 and v14.10.1

Additional information

Problem does not occur when using NPM to install the CLI package.

Even though Yarn informs that the binary was installed, it's unavailable. Example installation log:

success Installed "@vue-storefront/cli@2.0.3" with binaries:
      - vsf
@sudo-at-night sudo-at-night added the bug Bug reports label Sep 15, 2020
@filrak filrak added this to Backlog in Next Core 1.0 via automation Sep 15, 2020
@Fifciu
Copy link
Collaborator

Fifciu commented Sep 15, 2020

Please open terminal and run:

yarn global bin

Then:

echo $PATH;

I bet you do not have path to yarn global binaries in your $PATH - that's why you cannot run it from each place. More about this here

To solve this you should modify your $PATH variable. You could use (just tested it on Ubuntu 20.04):

export PATH="$(yarn global bin):$PATH"

Unfortunately, it will work only for the current terminal. If you want to have it permanently, you want to modify your ~/.bashrc. More about this here

@sudo-at-night
Copy link
Contributor Author

@Fifciu Yep, that was the issue, thanks 🙂

Next Core 1.0 automation moved this from Backlog to Done Sep 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug reports
Projects
No open projects
Next Core 1.0
  
Done
Development

No branches or pull requests

2 participants