I thinknpm install and similar commands would already throw on unsupported Node versions when the package manager tries to install vite? If so, we don't need to add this to the template explicitly. It doesn't add any new information to the project, yet it may become a maintenance burden in the future.

I now use Node 18 to runpnpm create vue to create a project and executepnpm i, and no errors or prompts appear. It is not untilpnpm dev is executed that the error appears.

Therefore, if the required node version information is added to package.json, the user can be informed more clearly of the reason.

In fact, after Vite released 7, many people encountered this problem and raised issues.

Thanks. I took some further tests. It seems thatpnpm create doesn't check theengines field ofcreate-vue, andpnpm install ignores those in the dependencies, whilenpm warns in both cases.
Including an explicitengines field in the created project'spackage.json is indeed beneficial for users ofpnpm.