2 ms·

So far no issues with PHP other than the occasional turn it off and back on again. NPM? Wake up on a saturday morning and hot reload + react tools no longer wo

So far no issues with PHP other than the occasional turn it off and back on again. NPM? Wake up on a saturday morning and hot reload + react tools no longer works? F me. On the bright side I almost finished the front end, so I can casually mess around with the solution every few days as I do my daily work in laravel.

steve_adams_86 8y ago
Haha, fair enough. The other day I was getting this bizarre mismatch of versions of a dependency and I couldn't figure out how it could even matter. Like, who cares if they're two minor versions apart? Neither of them were global so there was no conflict for their parent modules. _That_ is the kind of stuff that kills me about npm. It can be really reeeaally hard to figure out what to do in those situations. Also, package.json is arguably a pretty gnarly way to organize... Well, everything? It's the kitchen sink of configuration, but it's supposed to be for managing packages. But no, you can also configure your packages in there, configure scripts for your application, etc. It's nuts. Even so, both of them are miles ahead of what we had 10 years ago!