You should add export PATH="$PATH:$(yarn global bin)"
to your ~/.bash_profile
or whatever you use. It would solve the issue.
Depending on how you installed it, Yarn’s global folder varies for some reason. You can follow this issue here.
More Related Contents:
- Npm Package Install Problem (found 23 vulnerabilities)
- Where does npm install packages?
- What is the meaning of the “at” (@) prefix on npm packages?
- npm – EPERM: operation not permitted on Windows
- Installing a local module using npm?
- What is the difference between Bower and npm?
- What does npm install –legacy-peer-deps do exactly? When is it recommended / What’s a potential use case?
- Maximum call stack size exceeded on npm install
- Use of @ symbol in Node module names [duplicate]
- Running NPM scripts sequentially
- npm WARN … requires a peer of … but none is installed. You must install peer dependencies yourself
- Can I install a NPM package from javascript running in Node.js?
- After installation of Gulp: “no command ‘gulp’ found”
- Uncaught ReferenceError: process is not defined
- Node.js Port 3000 already in use but it actually isn’t?
- Writing npm modules in TypeScript
- TypeError [ERR_INVALID_ARG_TYPE]: The “path” argument must be of type string. Received type undefined raised when starting react app
- Saving files locally with electron
- Webpack output is empty object
- How to close electron app via javascript?
- Webpack breaking change
- How to list npm user-installed packages
- What is the “module” package.json field for?
- How to Set port in next.js
- “You may need an additional loader to handle the result of these loaders.”
- Missing basic DOM types in TypeScript project
- Can’t install any NPM package, error 4058
- using requirejs to load npm packages
- JavaScript dependency management: npm vs. bower vs. volo [closed]
- How to use npm modules in browser? is possible to use them even in local (PC)?