I'd rather spend 3 hours writing my own small library than some unknown but non-zero number of hours in the future fixing my app because it was broken by an update in some upstream tool
Show this thread
-
I've been very happy maintaining Execute Program, which uses Express and React and not a lot else (e.g. it has its own 116-line database library). By contrast, I'm trying to update Destroy All Software from Rails 5.2.3 to Rails 5.2.4.1 and it doesn't even boot.
Show this thread
Sounds like you might have accidentally updated some other dependency at the same time? I'd be really shocked if updating to a patch version broke your app
-
-
The exception is coming from sprockets (Sprockets::Railtie::ManifestNeededError). I don't know whether Rails core considers that "part of" Rails, but I do.
-
It's maintained by Rails, but the dependency lives in your Gemfile, it's not something you get transitively from Rails itself. That error sounds like you pulled a major version bump of sprockets. Definitely not something that changed in Rails 5.1.3 -> 5.1.4
- 9 more replies
New conversation -
-
-
I wouldn't
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.