Migrate from CRA to vite

lakshz commented 3 months ago

Is your feature request related to a problem? Please describe.

CRA has become outdated with time and we would like migrate to Vite for the following reasons:

Faster build time. Hence, a better development experience
Optimized production builds
More compliant with modern/best practices
Vite actively maintained on github unlike CRA
The number of weekly downloads of Vite is very large as compared to CRA

Describe the solution you'd like Many articles on the internet show steps about the migration. Reference

Most of the packages should be compatible with Vite but some specific packages/scenarios, might require additional configuration to work with Vite. Make sure this is done.
Make sure we don't unintentionally change any extra configuration, other than switching to Vite. This can create future issues.
Make sure that any script configuration files are placed in a sub-directory of scripts/

Approach to be followed (optional) A clear and concise description of approach to be followed.

Additional context Add any other context or screenshots about the feature request here.

Potential internship candidates Please read this if you are planning to apply for a Palisadoes Foundation internship https://github.com/PalisadoesFoundation/talawa/issues/359

lakshz commented 3 months ago

I can work on this.

Cioppolo14 commented 3 months ago

@lakshz Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. We sometimes give exceptions for more urgent cases and sometimes we lose track, but the policy stands. You have reached your limit, please wait until your existing issues are closed before requesting more issues. You could unassign yourself from one of the other issues too.

pranshugupta54 commented 3 months ago

Reference: https://github.com/PalisadoesFoundation/talawa-admin/discussions/1838

palisadoes commented 3 months ago

@lakshz Please fill in the issue template fully. We need a better searchable record of why this is being proposed.

lakshz commented 3 months ago

Yes, updated the description.

github-actions[bot] commented 2 months ago

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

Cioppolo14 commented 2 months ago

unassigning due to no activity or open PR

meetulr commented 2 months ago

I would like to work on this.

meetulr commented 2 months ago

Got stuck somewhere and couldn't give much time😅... will try to finish it by the end of the week.

github-actions[bot] commented 1 month ago

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

palisadoes commented 1 month ago

@meetulr Are you still working on this?

meetulr commented 1 month ago

I'm sorry about this😓, I wasn't able to do anything recently due to unforeseen circumstances. I'm finally free after today. I will actively work on it throughout this week.

I totally understand if someone else wants to take this, as my limit is over😅. Otherwise, I'll be resuming the work.

meetulr commented 1 month ago

Working😅, will provide a final update if I'm unable to complete it by the end of the week.

Update: I'm sry about this😓. I kept getting tangled up in things, thinking I would have time soon to complete this... but I couldn't, now its gsoc time and I have to focus on my project.

I would love to have the opportunity to take it up again If this remains unaddressed after a while and if I'm sure that I have time for this. I'll unassign myself for now as I've taken enough time. Sry for the inconvenience again😔.

PalisadoesFoundation / talawa-admin

Migrate from CRA to vite #1864