Ryan McDonald

I've created a repo using a fresh Rails 5.1.6.2 install that reproduces the issue using SplitChunks defaults: https://github.com/RyanMcDonald/react-rails-ssr-webpacker-splitchunks/blob/master/config/webpack/environment.js

I found the issue and updated my sample repo with [the solution](https://github.com/RyanMcDonald/react-rails-ssr-webpacker-splitchunks/commit/da95e0236ba87ce8a5a3890c0292ded95945411f) that I found. It looks like react-rails's default `WebpackerManifestContainer` calls `Webpacker.manifest.lookup` instead of `Webpacker.manifest.lookup_pack_with_chunks` when SplitChunks is enabled,...

Unfortunately, the project I'm working on has an older resque-scheduler version so I am running into issues with your branch since it uses the latest, which introduced a breaking namespace...

@justinweiss I managed to test using the upgraded resque-scheduler version. The hooks are running now, but the assertions are failing. I can't seem to do a simple `assert_queued_in`.

>As a temp workaround you can specify yAxisId="0" (which is the default) on your ReferenceLine elements @ckifer Thanks for the suggestion, but this doesn't seem to work. I updated the...

>actually, I can't reproduce any issue in your sandbox. Aside from adding optional chaining to prevent undefined access, everything works as I would expect Having to add optional chaining is...

>Majority I think use strings as their dataKeys rather than functions so that also cuts down the number affected by this. It's still an issue with strings as keys because...