What would be your practical advices/tips to avoid creating the worse app who will require 5 peoples to rewrite the codebase every 3y, when having to create a middle-sized SPA in ReactJS in 2024?
It’s needs to be :
an SPA (statically hosted)
As performant as possible and not a nightmare to maintain
I’m planning on using React-Aria to ensure myself to have accessible components on micro-levels (and so it’s requires react-dom)
@tixie My main suggestion would be to use some standard tooling like Vite or Next.js (statically exported), which has two main advantages:
You won't have a million-lines Webpack config to maintain.
You're forced to stay on the relatively beaten path, without using esoteric tools that are more likely to break and that future maintainers are more likely to not be familiar with.
Add comment