The Javascript framework mess.
Prakhar Tandon
6 replies
React, Next, Remix, Gatsby, Angular, Vue, Svelte, Astro... and 1000000 more.
Was recently working with a 2-3 year old React package, which was based on React 16, hence was getting conflicts and it was basically not working. Reason? I was using React 18+. Struggled for an hour to fix that, was simply some type conflicts coz of the version change.
In this vast mess of frameworks and breaking change versions, what's your take?
Replies
Coro@zignis
I'd stick with react 18, and monkey patch the packages that are too old, or rewrite them and open a pr.
Share
Comment Deleted
The JavaScript framework ecosystem is indeed overwhelming, and keeping up with the constant updates can be a real challenge. My take is to choose the framework that best fits the project requirements and team skills, and to invest in thorough testing when upgrading versions to minimize conflicts.
All the ai responses in here! 🥱Anyway this has always been the case and is why I (as a solo developer) just prefer vanilla js.
popular include are React, Angular and Vue
In my situation, identifying and resolving the isitcool.co.uk type conflicts likely required thorough debugging and potentially adjusting your code or configuration to accommodate the changes in React 18+.