Automatically install dependencies on yarn start?
See original GitHub issueDevelopers less familiar with modern JavaScript likely have trouble understanding why an error message like this comes up after running yarn start
:
Would create-react-app
benefit from adding a check on yarn start
that ensures the latest dependencies are already installed?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Installing dependencies | Yarn
yarn install is used to install all dependencies for a project. The dependencies are retrieved from your project's package.json file, and stored in...
Read more >yarn - Installing dependencies and working with version control
To install dependencies, you have to run yarn install in the root of your directory to install all the dependencies for a project....
Read more >How to install all the dependency package in yarn?
The equivalent of $ npm install is just $ yarn (without arguments) to install all dependencies ...
Read more >Deployment doesn't automatically install dependencies - fails
You should be able to just keep your build command as yarn install && yarn build to guarantee it installs dependencies. It sounds...
Read more >Automatically Install NPM Dependencies on Git Pull
Finally, we need to run npm install for each changed package. As Git runs on the project root directory and the changed files...
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 FreeTop 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
Top GitHub Comments
If you ask me I would stick to option to show message but not install dependencies. Side-effects are always tricky to maintain.
I think we should improve this message. We already parse it so might as well add some friendly instructions.
I don’t think automatic installation is something we’d want to pursue. There are many details that are easy to get wrong: npm and yarn can break each other’s trees (and we don’t know which one the user used last), the dependency may still be missing in package.json and we might install a wrong version, there might be a typo so installing won’t help, etc.
With that in mind would you like to work on brainstorming how to improve this message for the most common cases?