Closed jakebailey closed 3 years ago
I released webpack-obfuscator@3.0.0-beta.0
with the support of webpack@5, but I dropped the support of webpack@4.
javascript-obfuscator
now is a peerDependency
.
I'll release webpack-obfuscator@2.6.0
with the support of webpack@4 and javascript-obfuscator
as a peerDependency
today too.
Thanks; I've tested it and it appears to work!
I'm not sure that this will play nicely with TS, but if you didn't want to completely drop webpack v4 support, I know that some support both and do checks to switch between implementations. For example, webpack-cli uses this to switch between behaviors: https://github.com/webpack/webpack-cli/blob/master/packages/utils/src/isWebpack5.ts
Support both 4 and 5 more complicated. The problem starts with the typings and ends with different API.
Unfortunate. Hopefully people are content to stay on v2 for webpack 4, then. (Clearly I'm already on 5. 🙂)
For @4 i'll publish version 2.6.0
.
Released version 2.6.0
for webpack@4. This is the version with a long lifecycle
Need more tests of 3.0.0-beta.0
version. If everything will be ok, I release a stable version in a few days.
webpack 5 is due to be released pretty shortly; this plugin works fine in webpack 5 at the moment but may not in the future due to deprecations in the API. Running the plugin shows me:
Because the obfuscator plugin appears to be modifying the assets directly. I don't know quite enough about webpack to know what all is involved.