Yarn’s roadmap for v2 and beyond: What to expect going forward
Let’s explore what the roadmap is dangling in front of us and what to expect in the coming year.
The long, winding road
What does the new roadmap entail?
Some of the new changes for v2 (nicknamed Berry) include:
- Overhauled log system with unique diagnostic error codes
- Lockfile and configuration format will become a strict subset of YAML
- Added support for plugins, including new commands
- Cache format will switch from Tar to Zip
- Yarn v2 will become an API. Internal components will be split into modular entities.
- Dropped Node 4 and Node 6 support
- Nested workspaces supported out of the box
- Fully atomic cache – run multiple Yarn instances on the same cache
- Various bug fixes
These 2019 goals will make Yarn a development-first tool. This means more Plug’n’Play characteristics.
Yarn v2’s development officially started. Yarn will become a modular architecture powered by plugins and written in TypeScript 🎉 https://t.co/XVpjeT9Blb
— Maël (@arcanis) January 24, 2019
From Flow to TypeScript
One of the most notable changes Yarn will make is switching its codebase from Flow to TypeScript.
Yarn is currently fully covered by Flow types, and to be honest it works pretty well for us – the key part being “us”. Because we want to make it as easy as possible for third-party contributors to shim in and help us maintain this awesome tool, we’ll switch the codebase to TypeScript. We hope this will help making the codebase feel more familiar than the projects your already contribute to.
Is Microsoft’s TypeScript quickly becoming the new standard, and if so, what will this mean for developers?
Ready for change?
So, when do these big changes arrive?
For now, v2 will expect to hit the scene in early February with a new open repository. However, a stable release won’t happen until summer 2019, so you still have plenty of time with your current version.
How do you feel about the new changes? Will they overhaul Yarn for the better?