Recent searches
Search options
Administered by:
Half my day today is going to be focused on the continued upgrade from Node 16, react-scripts, to 18 and Vite.
This is gunna be rough...
@hazz223 openRewrite for the win?
@shimo Interesting suggestion! I had forgotten about that tool.
I'm too far in now 
. But what I might do is trial it after the fact, to see if it could cope.
Honestly this project is nuts. Way more complex than it needs to be.
@hazz223 as long as it has some structure it should do the heavy lifting.
Another alternative is to use CodeQL to find instances to change.
Let me know how it went I am really curious.
@hazz223 I was just thinking today how to escape this constant dependency update hell that node applications are - any suggestions? Svelte? :D Sth else?
@superFelix5000 I do feel like it's slowly getting better. Much earlier versions of node (like 12) had loads of breaking changes between versions, while these later ones seem more "stable".
However, the ultimate solution to all of this is just make sure you're not using too many external libraries, and you update often.
This particular project hasn't been touched in like 2.5 years, and was built differently. So it's extra confused 