fix: specify own Node version as target when bundling config files

[SegaraRai]

Description

fixes #17291

I am uncertain if it is safe to specify node${process.versions.node} for target.
At least esbuild supports a notation like node22.2.0 and node99.999.9999, but I am not sure about the following points:

• Whether process.versions.node is always present and in X.Y.Z format (at least bun seemed to have this)
• Compatibility between esbuild and Node versions

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[bluwy]

This looks fine to me. I remember discussing with @patak-dev that we could derive from process.versions.node but decided otherwise to prevent potential compat issues. The linked issue seems to be a good argument to derive it still.

[SegaraRai]

I have noticed that the tests in this PR are not working (dynamic imports are not modified by esbuild at all!), and I am wondering what I should do about it.
Perhaps I should change I have changed to static import since all Node.js in the current CI support import attributes, but is it acceptable for the tests not to pass in the old (<= v18.19.x, <= v20.9.x) Node.js?

[SegaraRai]

CI failed, but I think it will succeed on re-run (I don't have permission to do that).

[bluwy]

but is it acceptable for the tests not to pass in the old (<= v18.19.x, <= v20.9.x) Node.js?

Could we add some node version checks so that we skip testing this case in older versions, and so it doesn't fail for devs using an older node version locally? (I think I saw some checks you did in the previous commits)

[SegaraRai]

By splitting the test file, the import attributes test can now be run conditionally.
I wanted to use dynamic imports in the test files for feature detection, but this was not possible because all imports in the test code are rewritten by Vitest (Vite).

Tested with v18.12.0, v18.19.0, v18.20.0, v20.12.0, and v22.0.0.
From v20.0.0 to v20.11.0, for unknown reasons, a problem occurred in another part of the system and the test could not be run.

[bluwy]

Looks great! Thanks for updating the PR. I think the test for now is fine and should be enough.

[bluwy]

/ecosystem-ci run

[vite-ecosystem-ci]

📝 Ran ecosystem CI on 051c2ac: Open

suite	result	latest scheduled
analogjs	❌ failure	✅ success
astro	❌ failure	❌ failure
nuxt	❌ failure	❌ failure
vike	❌ failure	❌ failure
vite-plugin-react-pages	❌ failure	❌ failure
vitest	❌ failure	❌ failure

✅ histoire, ladle, laravel, marko, previewjs, quasar, qwik, rakkas, remix, sveltekit, unocss, vite-plugin-pwa, vite-plugin-react, vite-plugin-react-swc, vite-plugin-svelte, vite-plugin-vue, vite-setup-catalogue, vitepress

[bluwy]

The analog fail seems to be something on their end. I think this is ready to go in the next minor.