New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Plugin ecosystem / discoverability #65

Closed

zigomir opened this issue May 6, 2020 · 2 comments

Contributor

zigomir commented May 6, 2020

As discussed in #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?

The text was updated successfully, but these errors were encountered:

Member

yyx990803 commented May 7, 2020 •

edited

Loading

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.

Contributor Author

zigomir commented May 7, 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.

zigomir closed this as completed

github-actions bot locked and limited conversation to collaborators

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.