Skip to content
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

Use Vite instead of create-react-app #1539

Closed
andchiind opened this issue Apr 9, 2024 · 1 comment · Fixed by #1900
Closed

Use Vite instead of create-react-app #1539

andchiind opened this issue Apr 9, 2024 · 1 comment · Fixed by #1900
Assignees
Labels
breaking-change A breaking change which introduces changes to the public APIs frontend Frontend related functionality improvement Improvement to existing functionality

Comments

@andchiind
Copy link
Contributor

Describe the improvement you would like to see
I would like use to try and use something other than create-react-app, since it has not been updated in 2 years. This means that it will not support new version of Typescript, including Typescript 5 which is already out. A potential alternative is Vite.

Here is the website: https://vitejs.dev/
And here is some relevant example code: https://vite.new/react-ts

How will this change existing functionality?
It will allow the frontend to be more updated in terms of its packages. There may also be new features in Vite that were not in create-react-app, which we will be able to make use of. We did not use a large feature set in create-react-app, so we should first start by making an equivalent basic Vite setup.

I am giving it the breaking-change label even though it might not necessarily affect other PRs.

How will this improvement affect the current Threat Model?
It will improve it as we will be able to keep our packages updated.

@andchiind andchiind added breaking-change A breaking change which introduces changes to the public APIs improvement Improvement to existing functionality frontend Frontend related functionality labels Apr 9, 2024
@oysand oysand added this to the Ready for users milestone Apr 28, 2024
@aeshub
Copy link
Contributor

aeshub commented Jul 1, 2024

This issue has automatically been marked as stale as there has been no activity for 60 days.

@aeshub aeshub added the stale This issue or pull request already exists label Jul 1, 2024
@andchiind andchiind removed the stale This issue or pull request already exists label Nov 18, 2024
@Eddasol Eddasol self-assigned this Dec 17, 2024
@Eddasol Eddasol linked a pull request Dec 18, 2024 that will close this issue
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change A breaking change which introduces changes to the public APIs frontend Frontend related functionality improvement Improvement to existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants