chore: specify the correct minimum node requirements

[himanshusinghs]

Proposed changes

The version constraint earlier was pretty broad and did not really encapsulate the correct minimum requirements when it came to v22 and v23. This commit fixes that.

Checklist

• I have signed the MongoDB CLA

[Copilot]

Pull Request Overview

This PR updates the Node.js version requirements in package.json to be more specific about supported versions, moving from a broad minimum requirement to explicit version ranges for Node.js 20, 22, and 23.

• Updates the engines.node field to specify exact supported version ranges instead of a single minimum version
• Establishes clear compatibility boundaries for Node.js v20.19.0+, v22.12.0+, and v23.0.0+

[Copilot]

The version constraint syntax is inconsistent. The third range uses '>= 23.0.0' while the first two use caret ranges (^). Consider using '^23.0.0' for consistency, or if you specifically need all v23+ versions, document why this range differs from the others.

Suggested change

	"node": "^20.19.0 || ^22.12.0 || >= 23.0.0"
	"node": "^20.19.0 || ^22.12.0 || ^23.0.0"

[himanshusinghs]

Versions >= 23.0.0 support requiring esm by default

[coveralls]

Pull Request Test Coverage Report for Build 16347477296

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 3 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.09%) to 77.304%

---

Files with Coverage Reduction	New Missed Lines	%
src/common/atlas/apiClient.ts	3	73.03%

Totals
Change from base Build 16299138293:	-0.09%
Covered Lines:	2825
Relevant Lines:	3611

---

💛 - Coveralls

[kmruiz]

Even if we decide to bundle everything into CJS, I think we need to specify the correct engine as there are libraries that we already use that complain when used in older versions from users that opened issues in this repo.

[fmenezes]

@himanshusinghs can you update the README.md file? There is a section where we mention minimum node version

[himanshusinghs]

Ahh yea thanks for reminding me of this - I will do that.

[himanshusinghs]

@fmenezes this is how I am thinking. Let me know if you'd prefer shorter / semver version of this. I thought a worded description might suite better.

[fmenezes]

Works for me

[gagik]

ideally we want to have lower limits but yes this reflects the current reality

[gagik]

I think this needs npm install to update package-lock?

[himanshusinghs]

Weird, I did that a bunch of time and it did not update my lockfile but its true that the lockfile is still with older version.

Its updated now - I was not on correct branch (too much switching 🤦)