Igor Savin
Igor Savin
@ljharb If the approach is to base supported version on desired libraries / syntax, it might make sense to start forming a wishlist for these. I'll start: 1) Modern testing...
@ljharb It's subjective, of course, but I would take DX over minimalism any day. Adjustable height table that you control by a handle mechanically is minimalistic, but pressing the button...
@ljharb No, problem with Jest wasn't that it had poor DX. Actually, its API was so good, that both `vitest` and `bun` pretty much copied it verbatim, and it still...
``` By avoiding that complexity, even at the cost of some DX, you save years of dev time later ``` Not necessarily. We've migrated our tests from Jest to Vitest...
> My tape tests have never once needed any significant migration on 500 projects, over a decade YMMV on that. I definitely had to do more changes to node-tap tests...
@ljharb People who use the framework can plan their upgrades.
Maintaining consistent breadth of supported surface. Any sufficiently complex library eventually reaches state where certain problems and behaviours only affect certain versions of Node. Providing predictable pace of obsoletion is...
@wesleytodd Sorry if it sounded heated, I am genuinely trying to understand the rationale behind a particular line of reasoning. It is not my intention to attack it. @ljharb is...
@ljharb Yeah, but as you've said, this is realistically very rare in Node ecosystem. If v6 works with Node 10-20, and v7 works with Node 12-20, I don't see a...
Sounds great! Should we start drafting the LTS strategy text then?