-
Notifications
You must be signed in to change notification settings - Fork 206
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.
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
Replace CRA with Vite or similar for NodeJS templates. #11262
Comments
Hi @rogersau Thanks for this feedback, which is very valuable to us, but we need to discuss internally cause we have partner dependency on the SDKs we used, will keep you informed if we are going to make improvement in future release. |
@rogersau do you happen to have a guide on how to switch from CRA to vite? btw. there seems to be at least some movement on that issue: |
We have already migrated the Tab Dashboard template from CRA to Vite in the pre-release v5.10.0 version. In future releases, we plan to migrate more templates and samples to Vite to enhance the development experience. |
thats great to see. Are you planning on migrating existing projects to vite with a future Teams Toolkit update or will this always be a manual upgrade for existing proujects? |
We are in the process of migrating all templates in the Teams Toolkit (TTK) from CRA to Vite. In future updates, you won't need to manually upgrade your existing projects. Instead, you will be able to scaffold the latest templates directly from TTK. |
Is your feature request related to a problem? Please describe.
The React with Fluent UI template utilizes react-scripts (CRA) as its tooling. This results in extremely slow debugging and hot reloads. resulting in a poor developer experience. I find myself often using the template the stripping out react-scripts and moving to vite.
I believe ensuring a rock-solid foundation for Teams App development will lower the barrier of entry for new developers looking to extend functionality within Microsoft Teams. It will also ensure organizations do not start their journey already with Tech debt in their stack.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: