chore(@astrojs/node): use Node.js for testing

[ematipico]

Changes

This PR moves @astrojs/node to use Node.js for testing

Testing

Tests should pass

Docs

N/A

[changeset-bot]

⚠️ No Changeset found

Latest commit: bf5669a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[matthewp]

its-happening.gif

[Princesseuh]

Would love to see if there's any differences in speed!

[ematipico]

This PR

Benchmark 1: pnpm test
  Time (mean ± σ):     17.103 s ±  0.678 s    [User: 26.434 s, System: 4.905 s]
  Range (min … max):   16.390 s … 18.307 s    10 runs

main

Benchmark 1: pnpm test
  Time (mean ± σ):      5.786 s ±  0.232 s    [User: 7.962 s, System: 1.420 s]
  Range (min … max):    5.520 s …  6.272 s    10 runs

[ematipico]

I am closing this for now because the regressions are concerning. Node.js runs tests in parallel, spawning a process for each test. While this decision is understandable, there should be a way to allow to run tests in one single process.

I opened a feature request here: nodejs/node#51548

[bluwy]

LGTM after fixing the conflicts and the small nit below.

[YoutacRandS-VA]

Apply