-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Research Migration Details #1576
Comments
Hey @sydneywalcoff! Thanks for taking this issue. To help keep everyone in the loop, please comment your Estimated Time to Completion (ETC) below! Thanks again! |
ETC: 3 days |
Progress: I completed the migration from a research perspective on a personal project. I'm now notating the application for EA. |
Hey @sydneywalcoff! Thanks again for taking this issue.
|
Hey @sydneywalcoff! Thanks again for taking this issue.
|
4 similar comments
Hey @sydneywalcoff! Thanks again for taking this issue.
|
Hey @sydneywalcoff! Thanks again for taking this issue.
|
Hey @sydneywalcoff! Thanks again for taking this issue.
|
Hey @sydneywalcoff! Thanks again for taking this issue.
|
Overview
The Create React App(CRA) deprecation leaves EA open to lack of support, security risks, and performance issues. To avoid issues moving forward, EA is migrating to use Vite as our build tool.
Action Items
new issue approval
columnResources/Notes
Vite Docs
Notes & Questions
Is our type checking and/or linting coming from CRA?
Process?
npm create vite@latest
npm i
then runnpm run dev
@testing-library
andreact-scripts
folder: products/statement-generator/build
tofolder: products/statement-generator/dist
Testing
@testing-library
which is most of them. I'm setting up a separate issue to migrate our testing stuff once that's completeThe text was updated successfully, but these errors were encountered: