Yarn's Future – v2 and beyond
github.com
Yarn's Future – v2 and beyond
1–10 of 239 posts
Re: Yarn's Future – v2 and beyond
#2> your previous yarn.lock will be silently migrated
I hope that's not that silent, because at that point, everybody who works on that project will have to upgrade as well.
That said, shipping the light-weight POSIX-like shell will make it a lot easier for scripts to be multiplatform. That's the improvement I'm looking forward to most.
Re: Yarn's Future – v2 and beyond
#3There appears to be a real movement to move from Flow to typescript. Is Flow dying?
Re: Yarn's Future – v2 and beyond
#4There appears to be a real movement to move from Flow to typescript. Is Flow dying?
Well, TypeScript at least is growing enormously. Whether Flow dies or not is up to its authors, but I think TypeScript is pretty much unstoppable today.
Re: Yarn's Future – v2 and beyond
#5> your previous yarn.lock will be silently migrated I hope that's not that silent, because at that point, everybody who works on that project will have to upgrade as well. That said, shipping the light-weight POSIX-like shell will make it a lot easier for scripts to be multiplatform. That's the improvement I'm looking forward to most.
We'll make sure to add a notice at runtime to make it clear (plus, a consequent diff at review).
Also note that we recommend using `yarn policies set-version` to enforce the version of Yarn used by everyone in your team with very little friction:
https://yarnpkg.com/en/docs/cli/policies#toc-policies-set-ve...
Re: Yarn's Future – v2 and beyond
#6There appears to be a real movement to move from Flow to typescript. Is Flow dying?
There have been several projects that were flow based that have moved to TS. I think the real litmus test will be if React eventually either includes TS types or is rewritten in TS.
Disclaimer: I work with TypeScript professionally.
Re: Yarn's Future – v2 and beyond
#7I’m glad that Yarn will continue. Npm has improved, but it’s still less pleasant to work with than yarn (which basically always does what I expect, not so for npm).
Re: Yarn's Future – v2 and beyond
#8> your previous yarn.lock will be silently migrated I hope that's not that silent, because at that point, everybody who works on that project will have to upgrade as well. That said, shipping the light-weight POSIX-like shell will make it a lot easier for scripts to be multiplatform. That's the improvement I'm looking forward to most.
We'll make sure to add a notice at runtime to make it clear (plus, a consequent diff at review). Also note that we recommend using `yarn policies set-version` to enforce the version of Yarn used by everyone in your team with very little friction: https://yarnpkg.com/en/docs/cli/policies#toc-policies-set-ve...
There's a feature I didn't know about - that's enormously useful, thanks! Now to remember applying that to all my different repo's...
Re: Yarn's Future – v2 and beyond
#9There appears to be a real movement to move from Flow to typescript. Is Flow dying?
Facebook (excuse me, bunch of FB employees from the Flow team) says no: https://github.com/facebook/flow/issues/7365#issuecomment-45.... Of course, that's exactly what I'd say if I was in charge of a dying project.
Edit: but, their main codebase is in Flow, and that sounds like a mess to migrate, so I wouldn't be _too_ worried. It might slow down, but I doubt it will become unmaintained anytime before Facebook gets sued out of business :-P
Re: Yarn's Future – v2 and beyond
#10There appears to be a real movement to move from Flow to typescript. Is Flow dying?
I tried Flow and TypeScript out about half a year ago in a client project and Flow was kind of painful and difficult to use, the updates, bug fixes and new features weren't coming as often as TypeScript's were, and maybe 70% of people I talked to were using TypeScript instead of Flow. Since then it's more like 90% now, and the TS team seems to be adding and announcing features faster than before, whereas I haven't heard about any new features in Flow. Maybe they're there, I'm just saying I haven't heard about them. This is all anecdotal but from what I've heard, it's very common. This is a big reason I chose TypeScript in Autumn. Also, VS Code has become the de facto free editor of JavaScript projects with a full set of professional-grade IDE features across the board, and VS Code has first-class support for TypeScript but only plugin-level support for Flow. Since Monaco is simply extracted from VS Code, that means I got all VS Code's IDE features for free when I embedded Monaco into Autumn, all I had to do was set the language to "typescript" and it just works. All these free and serious benefits of TypeScript's ecosystem kind of point to this conclusion that I've seen on HN and elsewhere over and over, that TypeScript has already won and Flow is on its way out.