The development experience was not nice with the studio and gulp tasks were a spaghetti mess and it was hard to know how to start. I played around with yarn v2 and it was actually working pretty well, so I decided to give it a try. There are no longer yarn cmd something commands to run specific stuff.
Typing yarn will resolve dependencies for all packages; typing yarn build will actually call the build command in each package, and typing yarn watch will start each package's watcher, and they should build correctly based on their dependency graph.
Don't spent time reviewing the "new files" in scripts/ folder, those are the exact same commands which were in the gulpfile and I just moved them out of the file. Files in the .yarn folder are there to provide a seamless experience for v2 (if you have yarn v1, typing "yarn" will just use the minified cli and v2 will be working)
I'd need other persons to give it a try to be sure it work as expected.
The development experience was not nice with the studio and gulp tasks were a spaghetti mess and it was hard to know how to start. I played around with yarn v2 and it was actually working pretty well, so I decided to give it a try. There are no longer
yarn cmd somethingcommands to run specific stuff.Typing
yarnwill resolve dependencies for all packages; typingyarn buildwill actually call the build command in each package, and typingyarn watchwill start each package's watcher, and they should build correctly based on their dependency graph.Don't spent time reviewing the "new files" in
scripts/folder, those are the exact same commands which were in the gulpfile and I just moved them out of the file. Files in the.yarnfolder are there to provide a seamless experience for v2 (if you have yarn v1, typing "yarn" will just use the minified cli and v2 will be working)I'd need other persons to give it a try to be sure it work as expected.