command not found: yalc
See original GitHub issueI have tried to add yalc using npm and yarn globally.
yarn global add yalc
npm i yalc -g
but the result is this:
command not found: yalc
I have tried restarting the machine and clearing node_modules.
OS: Mac OS 11.6.2 (Intel) Node: v16.13.0
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
yalc - npm
Start using yalc in your project by running `npm i yalc`. ... versions in other projects that you are working on in your...
Read more >Command not found after npm install in zsh - Stack Overflow
My user folder in Mac OS Catalina does not contain this .bash_profile . I cant find it with search either. After updating the...
Read more >yarn: command not found error [Solved] | bobbyhadz
To solve the error yarn: command not found, install the yarn package globally by running `npm install -g yarn` and restart your terminal....
Read more >npm command not found in zsh but found in bash - Ask Different
I'm quite new using MacOS and zsh. I've been reading that I must add $HOME/.nvm/versions/node/v12.22.1/bin to my .zshrc file but when I do...
Read more >Yalc, the `npm link` alternative that "does" work - Divotion
Without the yalc link .. the consequent npm install command fails due to Missing write access to ./.yalc/my-component-lib/node_modules.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The same thing was happening for me even though
yalcwas included when I ranyarn global list. Turns out I needed to addexport PATH="$(yarn global bin):$PATH"to my.zshrc. I don’t remember having to do this before but it worked.I had this issue and it resolved when I uninstalled nvm (node version manager)