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

[TASK] Vite.js migration #2681

Open
4 tasks
yurixander opened this issue Nov 29, 2024 · 1 comment
Open
4 tasks

[TASK] Vite.js migration #2681

yurixander opened this issue Nov 29, 2024 · 1 comment

Comments

@yurixander
Copy link
Member

Attempt migrating to Vite.js from Next.js for tangle-dapp first, the reasoning being that we don't really use Next.js' features and also Next.js' "Fast refresh" is actually slow. Vite.js uses modern ES modules and provides the benefit of instant hot-reloading due to its highly optimized HMR.

  • Get rid of Next.js' config
  • Implement basic Vite.js config just enough to get the project running
  • Adjust startup of the tangle-dapp project to use Vite.js instead of Next.js
  • Optimize Vite.js configuration after everything's set and done
@yurixander
Copy link
Member Author

The main idea here is that the migration itself should mainly consist of config file changes and minor refactoring if any within the actual codebase. Also, react-router-dom would need to be implemented to replace Next.js' app router.

If it actually starts to take more time than that, then we can consider more in-depth strategy for the migration, ex. as @AtelyPham mentioned: creating a new project and migrating on a step by step basis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Not Started 🕧
Development

No branches or pull requests

1 participant