Setting up the Vite Team

[yyx990803]

As we are getting a LOT of new users, the issues are also growing by quite a bit. Since I have to split my attention between Vue and Vite, I won't always be able to timely triage/review/merge issues here when I need to focus on other tasks at hand. I would like to ask the community members to lend me a hand in the routine maintenance of Vite. My hope is that we can build a team that is able to handle minor bug fixes and patch releases without my direct involvement.

Since we are just starting out, I'd like to keep it simple. Becoming a Vite "team member" simply means you are willing to allocate at least a few hours a week in contributing to the project's maintenance. That can be triaging issues, fixing bugs, reviewing PRs, and maybe cutting releases. You'll get maintain access to the Vite repo. Work can be coordinated via issues and the #core channel on Vite Discord.

I would like to nominate the initial team members: @matias-capeletto (patak on Discord), @underfin and @antfu. Note the nomination is because becoming a team member involves a certain level of responsibility and commitment, so this is based on past track record and known intention of long term future involvement with the project.

The above members are also welcome to nominate other contributors.

For anyone else who is interested in becoming team member:

• If you already have multiple previous contributions to the project or can demonstrate good understanding of Vite internals via a project you've worked on, awesome! Please let us know below.

• If you haven't made any contributions yet, register your interest below and just start helping out - build up some contributions over time and we will review the progress in a couple weeks.

I will be creating some documentation for the issue triaging and PR merging workflows so we can keep things organized!

Update

I've added workflow graphs for issue triaging / PR reviewing in the contributing guide.

[Shinigami92]

I could try to investigate some issues but I don't know if I would become a core member 😄 (a bit scared 😄)
I will start by reviewing some issues and provide help
Especially if someone needs help for TypeScript, please feel free to ping me

My current only vite related project is: https://github.com/Shinigami92/vite-plugin-ts-nameof

---

I would love if @antfu would become a core member 🥇
Also @underfin is already a name in my head ^^ (Ah cause: https://github.com/underfin/vite-plugin-vue2)

[Shinigami92]

My contributions:

• chore: introduce eslint-plugin-spellcheck #2603 (introduce spellcheck) (was really helpful to iterate over some files ^^)
• chore: provide a pr template #2608 (provide a pr template)

[dheimoz]

Vite is the future for development. Least I can do is help. I have to admit that I need to learn a lot before being helpful enough, but assisting is the least I can do to reciprocate the amazing job that @yyx990803 and the candidates have been doing.

I want to help.

[Aslemammad]

I'm interested in being in the team, I haven't made any contributions here, but I'd like and try to do so. 🎉💥

[stingalleman]

I would love to give you a helping hand! I have one merged PR and one open PR, both relating to the logger (#2520 and #2425). I've always wanted to help to manage a big open-source project. I'm very experienced with Git & Github.

I can also help with moderating the Discord server.
It'll be interesting to see how this will go!

[anncwb]

I am very interested in joining the team, although I did not contribute before.It’s okay if can’t join, I’m more than happy to write some plugins to help Vite users， I have been following this, from 1.0 to 2.0, and used a template project built by him [vben-admin] (https://github.com/anncwb/vue-vben-admin).
For this project, I have written a total of 8 plugins so far. Some new plugins are under development. I have been working hard for the ecology so that webpack developers can switch to vite.
Plugins that have been completed so far：

• vite-plugin-html
• vite-plugin-compression
• vite-plugin-imagemin
• vite-plugin-mock
• vite-plugin-svg-icons
• vite-plugin-theme
• vite-plugin-style-import
• vite-plugin-import-context - Archived

[Subwaytime]

Great Announcement!
The Community is thriving and there are a so many Plugins currently beeing created, which is awesome! 🎉
I would be interested in helping out in one way or the other, due to my knowledge of the Vite Ecosystem!
Atm there is one Plugin that i contributed to the Vite Community, but three others are on their way.
Those are more connected directly to the Plugin API.
Besides Github and Plugins, if any Moderation help is needed for Discord, feel free to let me know!
I'll try my best to help out wherever i can 💯

Plugin that is currently out and running:
https://github.com/subwaytime/vite-aliases
I also contributed a bit to vite-plugin-components from @antfu.

Nonetheless, hopefully a nice Team will gather to keep the community in check and the project growing! 🎉

[patak-dev]

Thanks @yyx990803! It has been amazing to be part of this community and seeing how much Vite has grown in the past months! Kudos to everybody for the work that has been done, from PRs, participating in discussions here, in Discord and Twitter, to building up the ecosystem with plugins, frameworks, and projects migrations.

I would like to nominate @GrygrFlzr from SvelteKit to become a team member. I think it is fundamental that members of all frameworks are closely involved in Vite. They already got a few PRs merged and have been quite active in the community (discussions, features requests, answering questions in discord). In case more time is needed, I hope that we could set up triage permissions as a stepping stone towards becoming part of the team.

[GrygrFlzr]

Thanks for the nomination. For context, I've worked on several SvelteKit-related issues both on the reporting side and the bugfix side, particularly #2435, #2441, and #2537. Given how integral Vite is to SvelteKit, I think it makes sense to also contribute back to the Vite project by helping the team manage the influx of reported issues and PRs.

[userquin]

Well, I suppose that at this point and after having been learning from @antfu I could make another effort to make vite even better in what I can help and if my knowledge of the ecosystem allows me, so I will do my bit as far as possible (also, a bit scared).

Plugins / Respositories I have been involved in:

• vitesse: contributor
• vite-plugin-pwa: contributor
• @vueuse: some minor PR done
• some polymer 1.0 PR (years ago, life is too short), some PR and suggestions to app-date-picker: polymer 1/2/3 md date picker

[takurinton]

I want to contribute to Vite. I'm still inexperienced, but I'm very interested in this tool. I'm particularly interested in creating plugins, and I'm still creating them, albeit privately. nice to meet you!!!!

I also launched Vite Japanese translation team ( vite-docs-ja ). I would like to contribute in translation and coding.

[wheatjs]

Hi, I'm interested in joining the team. I haven't contributed directly to Vite, but I've been helping people in the Vite server for quite a while now and have published a couple plugins

• vite-plugin-vue-gql
• vite-plugin-generate-exports

So I guess maybe put me in the "review in a couple weeks" category 😅

[axe-me]

I'm interested to be part of the team. I dived into vite source code few time recently, also writing some vite plugin for the community right now.
one of my work : https://github.com/axe-me/vite-plugin-node

[yyx990803]

I've given a number of folks who've expressed interest here triage access to the repo - you should've gotten an invite and can help with routine issue triaging/label following the workflow here. Thank you!

[haoqunjiang]

I plan to spend more time on vite recently, so I'd like to officially apply for the team membership, too.

I've recently made some progress on Vite testing framework integrations (https://github.com/sodatea/vite-test-example, https://github.com/sodatea/vite-jest), and would like to get more feature parity between Vite and Vue CLI soon.

[patak-dev]

Thanks! I added you to the triage role as a stepping stone. Great to see the Vite jest integration moving forward 🚀

[g-plane]

I'm interested to be a member or a collaborator of Vite, and I've contributed to Vite four times: https://github.com/vitejs/vite/pulls?q=+author%3Ag-plane .

I plan to improve toolchains and settings of Vite internal development. As an ESLint member, I'm also considering providing integration between ESLint and Vite by creating some third-party packages.

[patak-dev]

Thanks for your contributions @g-plane! I added you to the triage role in the Vite repository. We'll keep expanding the team as people become more involved. Smooth integration between ESLint and Vite would also be very welcomed by the community

[nihalgonsalves]

(As discussed in Vite Land with @Shinigami92 @patak-js) I'm interested in helping out – we're in-progress converting a large app from Webpack, and I've contributed here: #3053 #3054 #3056 :)

[patak-dev]

Thanks for these PRs again @nihalgonsalves and for your interest in Vite! I have added you to the triage role in the Vite repository. Let's discuss in Vite Land 👍🏼

[import-brain]

@yyx990803 I know it's been quite a long time since you posted this, but are you still looking for triagers?

I'm still in the process of learning Vite to an in-depth level, but I have experience triaging for Express.js.

[patak-dev]

Hey @import-brain! We are always looking for people to help with triage. I think it is now one of the areas where help is more needed. I think the best would be for you to start triaging issues, commenting on your findings on them, and state if you think they should be closed or any other feedback. We also have a #triage channel in https://chat.vitejs.dev. I hope we will see you around, and thanks for getting involved!

[import-brain]

Thank you so much for giving me steps on how I should proceed, guess I should get started! :)