Webpacker 4 about percy-capybara

[djones]

Hi @vitalinfo, sorry about the issues here. Which version of percy-capybara are you using?

[vitalinfo]

@djones 3.2.0

[vitalinfo]

@djones looks like I've found work around with webpacker configuration

[djones]

@vitalinfo good to hear!

Just a little follow up here... we've been working on v4, a new major version of percy-capybara. We've pre-released this new version and it does away with loaders, therefore your webpacker configuration shouldn't matter at all.

Here is our upgrade guide to help you migrate from percy-capybara v3 to v4.

[vitalinfo]

Thanks

…

On Apr 1, 2019, at 5:39 PM, David Jones ***@***.***> wrote: @vitalinfo <https://github.com/vitalinfo> good to hear! Just a little follow up here... we've been working on v4, a new major version of percy-capybara. We've pre-released this new version <https://rubygems.org/gems/percy-capybara> and it does away with loaders, therefore your webpacker configuration shouldn't matter at all. Here is our upgrade guide to help you migrate from percy-capybara v3 to v4 <https://docs.percy.io/docs/upgrading-to-v4>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#76 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHLLbqDo5v2MGvfzbKYQ_LbbEBXr4D3_ks5vchoTgaJpZM4cUd0_>.

[doutatsu]

@vitalinfo Could you provide what you did with your configuration? I am facing the same issue and v4 upgrade didn't help me I am afraid @djones

[vitalinfo]

@doutatsu I've added extract_css: true to the test webpacker.yml config

[doutatsu]

You saved me @vitalinfo! Spent a month upgrading to webpack 4 and thought I'll be stuck with Percy now. This fixes it, huge props to you!