Hacker News new | past | comments | ask | show | jobs | submit login

Your frustration with React and the npm ecosystem is common but easily remedied; try NextJs.



NextJS has been an absolute, undocumented nightmare at our company we've gone back to CRA and "hand rolled" SSR to retain our sanity.

It's one of those modern magic frameworks that when you need to step outside the simple hello world example app you spend most of your days chasing buggy behaviours mentioned on unresolved month old github issues.

When this happens, usually your only choice and suggestion is update to the beta version of some core library, which breaks tons of other packages that haven't yet been updated to the new rewritten API, rinse and repeat.

Never again.

To be honest, NextJS wasn't worse than the rest of the JS ecosystem, the problem is systemic.


Yikes. Your experience in no way matches mine, nor that of many others I've worked with over the years. Using NextJs doesn't absolve you of the responsibility to understand the fundamentals of how your webapp works, but IMHO / IME it strikes a great balance when it comes to DX and convenience, with direct extensibility and support to drop a layer down to do things by hand; IOW, yeah there's some magic but it's the good kind. I'd be very interested to hear more about your "nightmare", and what circumstances led to the painted-corner of depending on beta versions of core libraries. Care to elaborate?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: