Subscribe on changes!

Plugin ecosystem / discoverability

avatar
May 6th 2020

As discussed in https://github.com/vuejs/vite/issues/34, plugins could be named vite-plugin-xxx.

I published vite-plugin-proxy, because it's something I missed from webpack-dev-server.

Maybe it's useful to mention this in readme so users can discover / find such plugins. Would you take a PR that adds this into vite's README?

avatar
May 7th 2020

I'm still in the progress of formalizing what a vite plugin should look like and what the atuo loading behavior should be. For now I think it's best to keep it unlisted.

avatar
May 7th 2020

Makes sense. Also makes sense to wait for config file too. One note, currently when passing a plugin all output from vite is suppressed.