Yarn install does not install missing modules in node_modules
<!-- *Before creating an issue please make sure you are using the latest version of yarn.* --> **Do you want to request a *feature* or report a *bug*?** <!-- Is the feature a substantial feature request? Please use https://github.com/yarnpkg/rfcs --> Bug **What is the current behavior?** Missing module directories in node_modules are not installed when running yarn install after you get the message "success Already up-to-date". Please note that a work around is to always run yarn install --force, however that slows down yarn install if no new modules are needed. Also everything seems to work with yarn install if the node_modules directory is deleted. **If the current behavior is a bug, please provide the steps to reproduce.** <!-- If you can, provide a link to a public repository which contains the files necessary to reproduce this. --> 1. Add a module (i.e. gulp-concat) through yarn -> "yarn add gulp-concat" 2. Run "yarn install" until the quick return with "Already up-to-date" 3. rm -rf node_modules/gulp-concat 4. Run "yarn install" 5. It will quick return with the message "Already up-to-date" without reinstalling gulp-concat **What is the expected behavior?** If a module is missing from node_modules (i.e. directory is not there) yarn should install the missing module and not report everything is up to date. Think of a multi developer environment where one developer installs a module and updates the source control with the updated yarn.lock file and/or offline
Posted by classicspam on Dec 13, 2016, 2:14 PM
Tags
Related issues
- [BUG] Cowork (Windows): all Plan9 shares fail with "Plan9 mount failed: invalid argument" after Windows update KB5124008 (26200.9445) — uninstalling the KB fixe
- Feature Request: Auto-resume CLI session when usage limit resets
- Please deobfuscate the Python
- [Bug] MLX version of Gemma 4 26B fails to load: "Model type gemma4 not supported" (macOS)
- # 233 Developers Discussed Abandoning the Office Add-in Platform — An Open Letter on the Office.js Stability, Security & Trust Crisis
- [FEATURE] Allow users to configure which shell the Bash tool uses or inherit initial shell
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
reliability (Software)
[BUG] Cowork (Windows): all Plan9 shares fail with "Plan9 mount failed: invalid argument" after Windows update KB5124008 (26200.9445) — uninstalling the KB fixe
Feature Request: Auto-resume CLI session when usage limit resets
Please deobfuscate the Python
[Bug] MLX version of Gemma 4 26B fails to load: "Model type gemma4 not supported" (macOS)
# 233 Developers Discussed Abandoning the Office Add-in Platform — An Open Letter on the Office.js Stability, Security & Trust Crisis
[FEATURE] Allow users to configure which shell the Bash tool uses or inherit initial shell
Admin Materials and Surfaces
AMD Support
Yarn install does not install missing modules in node_modules
<!-- *Before creating an issue please make sure you are using the latest version of yarn.* --> **Do you want to request a *feature* or report a *bug*?** <!-- Is the feature a substantial feature request? Please use https://github.com/yarnpkg/rfcs --> Bug **What is the current behavior?** Missing module directories in node_modules are not installed when running yarn install after you get the message "success Already up-to-date". Please note that a work around is to always run yarn install --force, however that slows down yarn install if no new modules are needed. Also everything seems to work with yarn install if the node_modules directory is deleted. **If the current behavior is a bug, please provide the steps to reproduce.** <!-- If you can, provide a link to a public repository which contains the files necessary to reproduce this. --> 1. Add a module (i.e. gulp-concat) through yarn -> "yarn add gulp-concat" 2. Run "yarn install" until the quick return with "Already up-to-date" 3. rm -rf node_modules/gulp-concat 4. Run "yarn install" 5. It will quick return with the message "Already up-to-date" without reinstalling gulp-concat **What is the expected behavior?** If a module is missing from node_modules (i.e. directory is not there) yarn should install the missing module and not report everything is up to date. Think of a multi developer environment where one developer installs a module and updates the source control with the updated yarn.lock file and/or offline
Comments (0)
No comments yet. Start the discussion.