You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yarn is giving me too much trouble, and it's no longer so better as latest npm in speed, consistency and features. For example, it is not working well with nvm.
In fact, when using nvm in a library, the gulp link(npm link) will symlink the project folder to a global node_modules matching the node version being used (for eg: ~/.nvm/versions/node/v8.12.0/lib/node_modules/)
But running yarn install in demo/ app , is not linking to the library in that nvm-node-related global modules, but instead to /usr/local/lib/node_modules/<your-project>.
Mention any other details that might be useful.
npm option should default to true and save in .yo-rc.json as useYarn key
config/helpers#installDependencies() should consider that useYarn flag
update .travis.yml's cache section accordingly
The text was updated successfully, but these errors were encountered:
Bug Report or Feature Request (mark with an
x
)Desired functionality.
Yarn
is giving me too much trouble, and it's no longer so better as latestnpm
in speed, consistency and features. For example, it is not working well withnvm
.In fact, when using
nvm
in a library, thegulp link
(npm link) will symlink the project folder to aglobal node_modules
matching the node version being used (for eg: ~/.nvm/versions/node/v8.12.0/lib/node_modules/)But running
yarn install
indemo/
app , is not linking to the library in that nvm-node-relatedglobal modules
, but instead to/usr/local/lib/node_modules/<your-project>
.Mention any other details that might be useful.
npm
option should default totrue
and save in.yo-rc.json
asuseYarn
keyconfig/helpers#installDependencies()
should consider thatuseYarn
flag.travis.yml
'scache
section accordinglyThe text was updated successfully, but these errors were encountered: