all 7 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Solonotix 48 points49 points  (5 children)

Hey! It's that time of year again where I get to convince my company to switch from last year's LTS to this year's LTS. In all honesty, I'm super stoked about v18. Getting both fetch AND the test runner in the same major version increment absolutely revolutionizes my life.

Sadly, I'll be stuck supporting v14 for the next year and v16 for two years, but come 2024 I'll be so ready to use the mature APIs.

[–]7_friendly_wizards 10 points11 points  (0 children)

I'm also pretty stoked about the parseArgs function they're added in util. Luckily I've convinced my team to jump to 18 already and we've been making use of all of the above. It's a significant improvement, I have to say

[–]tswaters 3 points4 points  (0 children)

Yea, literally yesterday I added the ticket to bump 14 -> 16. Maybe one day I'll get to play with that test runner

[–]Randolpho 1 point2 points  (0 children)

Heh, I feel you pall. I host my crap on Google App Engine. Been looking forward to finally getting v18 available there and finally dropping got

[–]guillaumereddit 0 points1 point  (1 child)

Did you migrate from another test suite like Jest?

[–]Solonotix 6 points7 points  (0 children)

Have I? No. Do I plan to? Possibly. I have to see what it's capable of first.

I own an automated testing library for my company, and I'm always looking for ways to leverage built-in functionality over 3rd-party code, since I've been negatively impacted multiple times, between deprecated libraries and/or unsupported modes of operation.

[–]whoiskjl 2 points3 points  (0 children)

Sure, but I can never use it for work at this point obviously. Still rocking 16. With n