feat!: move packages to ESM first

[userquin]

This PR moves @intlify/bundle-utils and @intlify/unplugin-vue-i18n to ESM first (right now CJS) fixing packages exports in both packages.

Without this PR

@intlify/bundle-utils

@intlify/unplugin-vue-i18n

With this PR

@intlify/bundle-utils

@intlify/unplugin-vue-i18n

[userquin]

This is about removing the extra required .default when requiring vite or webpack plugin (I don't use default export anymore to avoid this, you can remove the hack, run pnpm build && pnpm pack from the package and upload the generated tgz to https://arethetypeswrong.github.io/ or just check https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/docs/problems/FalseExportDefault.md):

const webpack = require('@intlify/unplugin-vue-i18n/webpack').default

[kazupon]

Look good to me!
Thank you! ❤️

[Tofandel]

@userquin What is the tool that you used to detect those problems?

[userquin]

@Tofandel I use publint and arethetypeswrong, both can be used with its own CLI, but I use their web version for a quick look at package exports.

arethetypeswrong will use use TypeScript to apply resolutions for node10, node16 and bundler module resolutions: will show the trace and some hints with the problems and how to solve them.

Visit https://arethetypeswrong.github.io/?p=%40intlify%2Funplugin-vue-i18n%405.3.1:

• hints at top, there are more, check the folder in the repo (click for example on Masquerading as CJS )
• click Details at bottom, you will see the resolutions for each entry point (subpackage exports) with every module resolution and the visible problems can be found in last entry "problems".

Daniel Roe added arethetypeswrong CLI workflow to Nuxt and later I added it to UnoCSS:

• test: add additional attw test for built packages nuxt/nuxt#30206
• test: add additional attw test for built packages unocss/unocss#4322