-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatibility with hard-source-webpack-plugin… #21
Comments
Hey @tdd - thanks for raising this :) If you're using SMP with webpack v4, then yeah - there's no guarantee that anything will work, just yet! Hopefully I should get the time to add support soon. If you're using it with another webpack version, though, then this should work. I'll have a look tonight, and see what the issue is. |
Right, so I've found an issue with HardSourceWebpackPlugin, which I've raised a fix for: #23 I'm just worried it doesn't perfectly describe what you described in this issue... Could you check out the branch and see if that fixes it for you? And if not, could you give me a bit more info? (Specifically, which webpack version, smp version, and HardSourceWebpackPlugin version you're using) |
Hey Stephen,
Thanks for the work! Looks promising, but it keeps breaking for me.
OTOH, I'm using this on v4, so this might be where the issue lies.
Didn't try on v3.
Best,
…On Thu, Mar 8, 2018, at 01:20, Stephen Cook wrote:
I'll assume this is complete with #23[1] (there are some tests
verifying this now with #24[2])> But let me know / reopen this if you're seeing any more issue
— You are receiving this because you were mentioned. Reply to this
email directly, view it on GitHub[3], or mute the thread[4].>
--
Christophe Porteneuve
[email protected]
Links:
1. #23
2. #24
3. #21 (comment)
4. https://github.com/notifications/unsubscribe-auth/AAAOqPXWz1210xAyZXBwVxgzi7yshwnNks5tcHk9gaJpZM4ScCkB
|
Doesn't work for me with |
This doesn't seem to be fixed:
|
Not fixed in 1.3.1 with webpack watch
|
Thanks for your comments everyone. Will reopen and try and find some time to investigate But I'm a little stretched for time with this, so would appreciate if anyone else has time to poke around at the failure too |
any update on this? Is there a way to make this work otherwise? |
still not working: |
still not working well: |
Hey there!
This plugin is awesome, unfortunately it seems to break another fav plugin of mine, hard-source-webpack-plugin, that is currently the most effective caching layer Webpack has (including v4). First run will work fine, later runs, once a cache exist, will break when this plugin exists.
This may be due to its not properly using v4’s plugin API yet? No idea. Still, this prevents me from using it everywhere right now. It'd be super sweet if you could coordinate with HS' author to figure this out.
Thanks a ton!
The text was updated successfully, but these errors were encountered: