feat!: bump minimum node version to 18 and match Vite 5 requirement

[ghiscoding]

Description

• this PR bumps Node (and @types/node) to 18+ or 20+ which is the same as Vite 5 new minimum requirement
• this change was announced in the Vitest 1.0 roadmap but was not yet bumped since 1.0 beta came out, this PR fixes that

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
  • the reference is Vitest 1.0 roadmap
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Note
~I ran pnpm install but there were too many changes, so I looked at my change in particular and applied it manually to the pnpm-lock.yaml to avoid having too many unrelated changes in the lock file

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

I used the exact same PR title that Vite used in this Vite 5 PR

Why create this PR?

I created this PR because I noticed that after upgrading to 1.0 Beta, my pnpm lock file changed in my project but was still showing a minimum requirement of Node 14 even though I did see that it was mentioned in the 1.0 roadmap that this will be bumped to 18 to match Vite 5 as shown below

One thing that should be mentioned is that Vitest 1.0 release will drop support for Vite 4 and Vite 3 since it relies on optimizeDeps having noDiscovery option. This also means Vitest will not support Node.js 16 anymore.

So, I went with creating this PR and used exactly what Vite 5 has set in their Node engine requirement here

"node": "^18.0.0 || >=20.0.0"
and @types/node peerDependencies here

"@types/node": "^18.0.0 || >=20.0.0"

Extra Notes

Please note that the CI workflow(s) are still being tested against Node 16 and 18, this should probably be changed to Node 18, 20 but that should probably be done in a separate PR (for example this PR #3492 was opened a while ago but never merged)

vitest/.github/workflows/ci.yml

Lines 57 to 60 in edddc8f

	strategy:
	matrix:
	os: [ubuntu-latest]
	node_version: [16, 18]

[netlify]

✅ Deploy Preview for fastidious-cascaron-4ded94 ready!

Name	Link
🔨 Latest commit	619bea5
🔍 Latest deploy log	https://app.netlify.com/sites/fastidious-cascaron-4ded94/deploys/65367af50ab1b70008b41286
😎 Deploy Preview	https://deploy-preview-4296--fastidious-cascaron-4ded94.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[ghiscoding]

@sheremet-va I'm not sure how you usually update the pnpm lock file but the case of this PR after running pnpm install, the lock file changed a lot and all CI tasks fails. I could remove the lock file change from the PR or you could take over the PR and update it yourself, feel free to go ahead with changes or let me know if a special pnpm command must be run to fix this problem (I mean I could go by hand to update the lock file but I would still prefer to do it through pnpm lol)

EDIT

I reverted to the previous lock file and manually updated the Vitest peer dependency, this is looking a lot better now and more focused with current PR change

EDIT 2

I think some tests are failing because 1.0.0-beta.2 was not published to npm (I've opened a separate issue #4297 for that), as we can see in below print screen

test/setup test:  ❯ tests/console-setup.test.ts  (1 test | 1 failed) 1395ms
test/setup test:    ❯ tests/console-setup.test.ts > setup files console > print stdout and stderr correctly
test/setup test:      → expected '\n RUN  v1.0.0-beta.2 D:/a/vitest/vit…' to include 'stdout | setupFiles/console-setup.ts'
test/core test:  ✓ |core| test/lot-of-tests.test.ts  (1 test) 4ms
test/setup test:  ✓ tests/empty-setup.test.ts  (1 test) 4ms
test/core test:  ✓ |core| test/sequential.test.ts  (2 tests) 147ms
test/setup test:  ✓ tests/fixtures/console.test.ts  (1 test) 4ms
test/setup test: ⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯
test/setup test:  FAIL  tests/console-setup.test.ts > setup files console > print stdout and stderr correctly
test/setup test: AssertionError: expected '\n RUN  v1.0.0-beta.2 D:/a/vitest/vit…' to include 'stdout | setupFiles/console-setup.ts'

[Dunqing]

EDIT 2

I think some tests are failing because 1.0.0-beta.2 was not published to npm (I've opened a separate issue #4297 for that), as we can see in below print screen

test/setup test:  ❯ tests/console-setup.test.ts  (1 test | 1 failed) 1395ms
test/setup test:    ❯ tests/console-setup.test.ts > setup files console > print stdout and stderr correctly
test/setup test:      → expected '\n RUN  v1.0.0-beta.2 D:/a/vitest/vit…' to include 'stdout | setupFiles/console-setup.ts'
test/core test:  ✓ |core| test/lot-of-tests.test.ts  (1 test) 4ms
test/setup test:  ✓ tests/empty-setup.test.ts  (1 test) 4ms
test/core test:  ✓ |core| test/sequential.test.ts  (2 tests) 147ms
test/setup test:  ✓ tests/fixtures/console.test.ts  (1 test) 4ms
test/setup test: ⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯
test/setup test:  FAIL  tests/console-setup.test.ts > setup files console > print stdout and stderr correctly
test/setup test: AssertionError: expected '\n RUN  v1.0.0-beta.2 D:/a/vitest/vit…' to include 'stdout | setupFiles/console-setup.ts'

I created #4245 to fix this test case failing

[ghiscoding]

@sheremet-va is there anything left to do in this PR for it to be merged or are you just waiting for the next beta release to merge it? I'm just wondering if there's anything I need to change. Thanks