chore(main): release 18.0.0

[github-actions]

🤖 I have created a release beep boop

18.0.0 (2025-05-06)

⚠ BREAKING CHANGES

• command names are not derived from modules passed to command.
• singleton usage of yargs yargs.foo, yargs().argv, has been removed.
• minimum node.js versions now ^20.19.0 || ^22.12.0 || >=23.
• yargs is now ESM first

Features

• commandDir now works with ESM files (#2461) (27eec18)
• locale: adds hebrew translation (#2357) (4266485)
• yargs is now ESM first (d90af45)
• zsh: Add default completion as fallback (#2331) (e02c91b)

Bug Fixes

• addDirectory do not support absolute command dir (#2465) (3a40a78)
• allows ESM modules commands to be extensible using visit option (#2468) (200e1aa)
• browser: fix shims so that yargs continues working in browser context (#2457) (4ae5f57)
• build: address problems with typescript compilation (#2445) (8d72fb3)
• coerce should play well with parser configuration (#2308) (8343c66)
• exit after async handler done (#2313) (e326cde)
• handle spaces in bash completion (#2452) (83b7788)
• parser-configuration should work well with generated completion script (#2332) (888db19)
• propagate Dictionary including undefined in value type (#2393) (2b2f7f5)
• zsh: completion no longer requires double tab when using autoloaded (0dd8fe4)

Code Refactoring

• command names are not derived from modules passed to command. (d90af45)
• singleton usage of yargs yargs.foo, yargs().argv, has been removed. (d90af45)

Build System

• minimum node.js versions now ^20.19.0 || ^22.12.0 || >=23. (d90af45)

---

This PR was generated with Release Please. See documentation.

[bcoe]

Candidate version installed to npm i [email protected] try it out.

[bcoe]

Latest beta build + [email protected].

[bcoe]

I'm thinking, wait until some time after April 19th when Node 18 goes EOL.

[shadowspawn]

Are you planning any other announcement about prerelease available now? I was thinking I could create and pin an issue pointing here for further details and promoting npm install yargs@next?

[bcoe]

Are you planning any other announcement about prerelease available now?

That's a good idea.

I was thinking I could create and pin an issue pointing here for further details and promoting npm install yargs@next?

Yes, please do 👏

Perhaps we wait longer than April 19th 30th, to give folks a chance to see this. My concern is less the Node 18 EOL, and more the fact that our version range asks for specific versions of 20 and 22.

[shadowspawn]

(Not the critical date but to clarify, Node 18 goes EOL on 2025-04-30 according to https://github.com/nodejs/release#release-schedule)