Replace webpack by maintaining the functionality that is currently present

[erikyo]

From a conversation this morning on slack with @gziolo where he was telling me that actually wp-scripts does (also) this:

• Copy files #2
  • image
  • fonts handling
• Dependencies and modules #4
  • CSS processing, including PostCSS, SASS, CSS modules,
  • Minification
• i18n #8
• Hot Module Replacement integration should work #9
• entry points are automatically collected from block.json files #5
• users can provide their own config overrides #6

Some things are already there but I keep it as a checklist of the main features

ref. https://github.com/WordPress/gutenberg/blob/trunk/packages/scripts/config/webpack.config.js

[gziolo]

users can provide their own config overrides to webpack, PostCSS, cssnano, browserslist, babel

That part might not be needed when using Vite, but it illustrates the level of customization that projects use to fulfill their use cases.

[erikyo]

You are right, though. Indeed, would be cool to provide the possibility to configure the bundle. Vite has a some options, such as whether to use its internal minifier or Terser, whether to use SWC or Rollup, etc. especially the latter would be interesting

[erikyo]

Perhaps the best approach is to create configurable vite/rollup plugins (they use the same standard).

Yesterday, I have read a little bit about, and I must say that also the resolver part is very improvable, I add here some references:

• https://vitejs.dev/guide/api-plugin#universal-hooks
• https://rollupjs.org/plugin-development/
• https://medium.com/@lior_amsalem/write-your-own-vite-plugin-42aceac9887c
• https://javascript.plainenglish.io/make-your-first-vite-plugin-de5a37ad9fa9