Artem Batura

Hi! Thank you for reporting this. I'll try to reproduce it later but it's would be good if you will you provide the minimal reproduction example.

I'm preparing changes which should help you with this bug. Keep updated

Also thank you for reporting this, after investigating I understand that it's a serious bug which can cause to be plugin fully useless. Found and other smaller bug...

Hi. Thank you for the kind words. Plugin is agnostic to the resource types but there exists rare case where modification of original modules doesn't work because some loaders create...

Hi man. It's a good idea, I think we can add new argument `path` and leave `filename` as exists. It's will be more handy, because you will don't need to...

Yeah it's a better idea. And bumping new major version it's a good point. I just don't know how to deal with version for webpack 4 because we have two...

@epegzz Should be fixed in #55. You can test before it's got released by installing `modify-source-webpack-plugin@next`. Version `3.0.0-rc.0`. Now we will have single version of plugin for webpack 5 and...

Bump!

Тем более, если Facebook уберет поддержку кода PHP на HHVM в будущем, то JPHP будет хорошим аналогом и будет возможность устроить популяризацию JPHP

Такая же проблема и при добавлении/удалении/вырезки компонентов на форме, UXTabPane реагирует почему-то