build!: bump targets

[Shinigami92]

Description

Bumping targets

Additional context

According to this table https://kangax.github.io/compat-table/es2016plus/ it is mostly safe to go with ES2020
The lowest node version would be v14.6.0. This is also the requirement in package.json and in vitest and other "modern" packages.

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[sapphi-red]

I think you forgot to change this one.

vite/packages/plugin-legacy/tsconfig.json

Line 6 in c86329b

"target": "ES2018",

[Shinigami92]

I think you forgot to change this one.

vite/packages/plugin-legacy/tsconfig.json

Line 6 in c86329b

"target": "ES2018",

I did not forgot that, I left that over due to this is the legacy plugin

[sapphi-red]

I think you forgot to change this one.

vite/packages/plugin-legacy/tsconfig.json

Line 6 in c86329b

"target": "ES2018",

I did not forgot that, I left that over due to this is the legacy plugin

IIUC plugin-legacy enables bundled code to be able to run in legacy browsers, but the plugin itself does not run in legacy browsers (it requires node 14.16+).
So I think it could be changed.

[Shinigami92]

IIUC plugin-legacy enables bundled code to be able to run in legacy browsers, but the plugin itself does not run in legacy browsers (it requires node 14.16+). So I think it could be changed.

@patak-dev Could you approve this statement?

[patak-dev]

@Shinigami92 yes, internal Vite plugins will also require Node 14.16+, same as core.