Curl doesn't add libproxy due to its quality issues

Re:Curl doesn't add libproxy due to its quality issues by folkrav on Sunday October 23, 2022 @10:22AM (#33307237)

> You don't need Jest. You can use buld-in test runner since Node 19.0 (https://nodejs.org/api/test.html)

v19 was released 5 days ago. Barely had time to register this was a thing, let alone migrating our 3500+ unit test+ 300 integration test suite lol

> 1/ You do not need to use https / https module directly. You can use Fetch API since Node 17.5 ( https://nodejs.org/api/globals.html#fetch ). > 2/ You do not need an external CLI parser. You can use build-in CLI parser since Node v18.3 ( https://nodejs.org/api/util.html#utilparseargsconfig )

Lots of production environments tend to sit on latest LTS. v18 _just_ hit LTS, up to last month it was v16. Those weren't really an option for all these projects until then.

[ Parent | on HN ]

Re:Curl doesn't add libproxy due to its quality issues by lightswitch05 on Sunday October 23, 2022 @10:33AM (#33307321)

Yes, my library absolutely has to support the LTS version of Node, and I run the tests against all supported versions to ensure compatibility. So, one day I can use the nice things people are mentioning, but it will be years from now.

[ Parent | on HN ]