chore(vite): remove main and module fields

[ydcjeff]

Description

Since Vite 3 supports Node 14+ and there is already an exports field which takes more priority than main and module so Node will only from exports and will never reach to main and module field entries.

cc @bluwy

Additional context

---

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.

[antfu]

I see no harm to keep them for a while longer for compatibility, for example, eslint seen failed to read it.

[bluwy]

Make sense to me. main won't be used at all with exports in node14, and most modern bundlers would read from exports than module these days.

My side project is also suggesting it as well :)

Thanks for catching this

[ydcjeff]

Unfortunately, there isn't a proper solution to fix the linting error. The rule node/no-missing-import updated was at the end of 2020 and also rule import/no-unresolved didn't support omitting main field yet (import-js/eslint-plugin-import#2132).

So, I will close this and let's keep them for a while.