Cleanup the dependency graph

[Norbiros]

There is a really nice initiative called e18e, whose goal is to clean up, optimize, and speed up libraries and their dependency trees in the node ecosystem. Given that this project is ESM-only and requires Node.js >=22.18.0, we could replace some things with native Node.js APIs, better alternatives, etc. to make hey-api safer and lighter.

Quick replacements (i'll open PRs for those):

• ansi-colors could be replaced with the native Node.js API
  Resolved by: refactor: replace ansi-colors and color-support with native styleText #4291
• color-support could be replaced with the native Node.js API
  Resolved by: refactor: replace ansi-colors and color-support with native styleText #4291
• semver could be replaced with verkit - Replace semver with verkit e18e/ecosystem-issues#277
• is-yaml - https://e18e.dev/docs/replacements/js-yaml

Harder, so you probably don't have to do any of these:

• open - users don't need this dependency most of the time. It could be moved to peer dependencies, and if open is not detected, you could just print the URL
• cross-spawn - make it an optional dependency, since you might not need a formatter
• @jsdevtools/ono

Tip: I really recommend this site: https://npmgraph.js.org/?q=%40hey-api%2Fopenapi-ts, so you can visualise your dependency tree.

[pullfrog]

  ^{｜ Build this ➔ ｜ Make a plan ➔}

[mrlubos]

@Norbiros thanks! verkit looks interesting and I've commented on your first pull request already. @SukkaW could tell you why replacing js-yaml is not going to happen, we looked at it before. Also, e18e says it appears to be unmaintained but that's false. I'm actively looking at removing / replacing @jsdevtools/ono. Didn't consider open and cross-spawn

[SukkaW]

@mrlubos @Norbiros

js-yaml is consistently 20% faster than yaml on large OpenAPI YAML spec, which makes Cloudflare OpenAPI spec generation time go from 11s down to 9~10s.

This is because yaml uses Generator in its internal parse implementation, where JavaScript runtimes/engines need extra overhead to be compliant with the ECMA-262 spec. js-yaml, on the other hand, uses normal loop/recursion where JavaScript runtimes/engines are already optimized to extreme.

[mrlubos]

@char0n check above