Move to ESM

[lev875]

#227

• Added type: module to all package.json files
• Swapped jest for vitest
  • Updated snapshots
  • Updated tests
  • Split fixtures in esbuild and webpack plugins into cjs and esm directories
    • Both esbuild and webpack are determining the module type based on nearest package.json file. When I switched these plugins to type: module in their respective package.json files it broke some tests, because the bundlers started treating the files as esm and not cjs like before. That's why I've split the fixtures directories and added package.json files to force the correct module type during bundling tests.
  • Added tests for esbuild and webpack using esm configs
• Updated code to esm
  • Rewrote all imports to esm style
  • Rewrote loadPlugins to use promise based dynamic import() instead of require()
  • Rewrote package.json import in create-help.js using createRequire to avoid using experimental import ... assert syntax
• Updated the ci workflow

Notes:

• Some tests are generating temporary files inside 'fixtures' directory. If you do not exclude 'fixtures' directory in vitest watch path, it will result in tests infinitely triggering reruns in watch mode.
• I took a liberty of rewriting a couple of tests from if (stmt) { it(...) } to it.skipIf(!stmt)( ... ) so it looks a bit cleaner and the runner reports these tests as skipped

[ai]

Can you run Prettier on changed files?

I have it in VS Code. But you can install to the project, run, and uninstall.

[lev875]

Ah, damn, I did eslint --fix but forgot about prettier. I've installed it globally and ran pnpm exec prettier **/*.js --write, should do the trick.

[ai]

Suggested change

	it('should work with commonjs config', async () => {
	it('works with commonjs config', async () => {

and all other tests

[lev875]

Fixed by c17c150