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
-
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
-
-
I don't know where Rails ends and Sprockets begins but I'm supposedly an expert in this technology. It's all Rails to me. Everything in app/assets/config is Rails; manifest.js is definitely Rails. That new replacement for sprockets that uses webpack is also Rails.
-
The only distinction I'm trying to make is "thing that is a dependency of the gem called `rails`" vs "thing that is in your gemfile which is also maintained by the rails org"
- 7 more replies
New conversation -
-
-
Er 5.2.3 rather. Either way it sounds like you need to lock down your sprockets version to 3.x
-
Don't get me wrong, upgrading Rails can be a major pain for major releases. But if your app broke from updating a patch version that is a bug.
End of conversation
New conversation -
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.