Patrik Bóna

This doesn't affect only webpacker, but the webpack integration via jsbundling-rails, too. Steps to reproduce: ``` rails new action-text-webpack-test --javascript webpack cd action-text-webpack-test rails action_text:install ``` `yarn build` fails now:...

I'm experiencing the same issue. I solved it by writing `http://localhost:3035` to `~/.puma/webpack-dev-server.memberful` AND rebooting the computer. Changing the file content (and restarting puma-dev) without rebooting did not help. Also,...

I'm having exactly the same issue and while I was googling it I came here. @westonganger Did you try to debug it? Did you find any solution?

I did some debugging and I found out that if you did not generate binstubs for your project, then rbenv-binstubs generates shims for all files in `~/your_project/bin`. So if you...

Thank you @madumlao! Unfortunately I'm not able to reproduce the original issue anymore so I can't test if the new version fixes it.

@Petercopter, that error is coming from the Intercom widget. For 422 responses, I see an error coming from `frame.134abfc8.js`. I'll probably open a ticket for them.

The Intercom widget listens to `turbo:load`, `turbo:visit`, and `turbo:before-cache` events. Turbo doesn't fire any of these events during unsuccessful form submission, so the widget can't prepare itself for the DOM...

@summera It looks like this was never fixed. When I remove our workaround, the Intercom widget fails on unsuccessful form submission.

We have the same issue. @pedantic-git thank you for posting the workaround, it works great!

@choran @pedantic-git I just tested it on our site and it indeed works very well with Turbolinks 5. Thank you!