The connection_pool gem changed their API, which caused a breakage in our react-rails gem. It turns out though, we're not actually using react-rails anymore. It's primarily for React server-side rendering, which we don't do. Our React code is bundled as normal Javascript via our usual asset pipeline. So, to resolve the gem incompatibility, we remove react-rails altogether. Neat! |
||
|---|---|---|
| .. | ||
| cache | ||
| gems | ||
| javascript | ||