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 add [package] and yarn install resolve packages and copies the node_modules structure. Dependant on flags it writes package.json and yarn.lock as-well.
If the current behavior is a bug, please provide the steps to reproduce.
N/A
What is the expected (extended) behavior?
The idea would be an extra flag --warmup, adding or installing packages with this flag would only write to the .yarn-cache, ignoring the link step. Since nothing would be linked it would also skip writing the package.json and yarn.lock file.
I believe it might come in useful while setting up a development environment for the first time, while getting everything up and running you could already warmup the .yarn-cache if you know for example a lot of your future projects will have react, babel, webpack,... dependencies before even ever starting. In the same way it could come in handy in some other smaller cases, ex. installing (preparing) dependencies from anywhere without being in the correct directory.
--warmup flag felt more intuitive to me, but it could of course just be yarn warmup [package] as well.
Please mention your node.js, yarn and operating system version.
N/A
The text was updated successfully, but these errors were encountered:
ghost
changed the title
--warmup flag to only write cache
[feature] --warmup flag to only write cache
Oct 18, 2016
Do you want to request a feature or report a bug?
Feature
What is the current behavior?
yarn add [package]
andyarn install
resolve packages and copies the node_modules structure. Dependant on flags it writespackage.json
andyarn.lock
as-well.If the current behavior is a bug, please provide the steps to reproduce.
N/A
What is the expected (extended) behavior?
The idea would be an extra flag
--warmup
, adding or installing packages with this flag would only write to the.yarn-cache
, ignoring the link step. Since nothing would be linked it would also skip writing thepackage.json
andyarn.lock
file.I believe it might come in useful while setting up a development environment for the first time, while getting everything up and running you could already warmup the
.yarn-cache
if you know for example a lot of your future projects will havereact
,babel
,webpack
,... dependencies before even ever starting. In the same way it could come in handy in some other smaller cases, ex. installing (preparing) dependencies from anywhere without being in the correct directory.--warmup
flag felt more intuitive to me, but it could of course just beyarn warmup [package]
as well.Please mention your node.js, yarn and operating system version.
N/A
The text was updated successfully, but these errors were encountered: