rally25rs
commented
6 years ago This doesn't happen under normal operation:
~/Projects/yarn-test2 🐒 cat package.json
{
"name": "yarn-test2",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"keywords": [],
"author": "",
"license": "ISC",
"dependencies": {},
"devDependencies": {
"standard": "^11.0.1"
}
}
~/Projects/yarn-test2 🐒 yarn add left-pad
yarn add v1.7.0
[1/4] 🔍 Resolving packages...
[2/4] 🚚 Fetching packages...
[3/4] 🔗 Linking dependencies...
[4/4] 📃 Building fresh packages...
success Saved lockfile.
success Saved 1 new dependency.
info Direct dependencies
└─ left-pad@1.3.0
info All dependencies
└─ left-pad@1.3.0
✨ Done in 0.99s.
~/Projects/yarn-test2 🐒 cat package.json
{
"name": "yarn-test2",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"keywords": [],
"author": "",
"license": "ISC",
"dependencies": {
"left-pad": "^1.3.0"
},
"devDependencies": {
"standard": "^11.0.1"
}
}
~/Projects/yarn-test2 🐒 ls node_modules/standard
AUTHORS.md LICENSE RULES.md bin eslintrc.json node_modules package.json
CHANGELOG.md README.md SECURITY.md docs index.js options.jsyarn must be picking up the --production or NODE_ENV=production flag from somewhere.
Maybe try running yarn config list and yarn run env and see if "prod" is in the output somewhere?
3dos
bug
Yarn removes packages from node_modules when adding new ones
I use standardjs as a linter in my IDE (Atom) and it requires the
standardpackage installed in devDependencies. When adding new dependencies, thestandardpackage is removed from the node_modules and I have to install it again each time.I tried to set my NODE_ENV to development writing
in
/etc/environmentan restarted my computer with no success.Having this issue on a MacBook Pro (High Sierra) with Yarn 1.7.0, Node 10.4.1