refactor: remove deprecated api for 3.0

[ydcjeff]

Description

• fix Remove @deprecated code #5842

Additional context

logDeprecationWarning is removed alongside with deprecated options though it is good to have that function as there can be deprecated options in the future. But, build is failing without removing that function.

---

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.

[Shinigami92]

Hey @ydcjeff 👋 could you update this PR? Then we can start to review and merge it.
If there are more stuff to do, we can open additional PRs for this task.

[Shinigami92]

I will switch this PR to draft, please switch back to ready for review when finished, then I can start reviewing

[Shinigami92]

I'm looking into the code and found

packages/vite/src/node/build.ts line 425 - 432, not sure if we should somehow just ignore this property? Maybe clone the object and remove the property from the clone?

packages/vite/src/node/importGlob.ts line 31 - 36, 136+

packages/vite/src/node/server/pluginContainer.ts line 120+ 🤔

packages/vite/types/hot.d.ts line 11 - 14

packages/vite/types/importMeta.d.ts line 12 - 17

[ydcjeff]

packages/vite/src/node/server/pluginContainer.ts line 120+ 🤔

This is about rollup deprecating their context function so I think we should keep this until rollup removes them?

packages/vite/src/node/build.ts line 425 - 432,

There is no output property in rollup's OutputOptions, so we can safely remove it?

[Shinigami92]

pluginContainer.ts line 120+

Ah yeah, I assume it's also correct here, because we are using Omit for these. So I just thought to quickly 👍

[Shinigami92]

Starts to look like ready to merge 🙂

there is no longer a mandatory request for a change

[ygj6]

I ran a global search locally and it looks good.

[patak-dev]

@antfu sorry, I merged the PR before seeing the on hold label. Was the label only about waiting until we start merging v3 PRs or is there something else that we should discuss about this?