Closed clydin closed 3 years ago
I can't seem to reproduce this, for example with target: ['web', 'es5']
. Are you using the latest version? If so, could you let me know a specific target setting that you see the issue with or, even better, provide a demo repository that triggers it?
As for false
, for checking compatibility we're now using the chunkLoading
setting when available so hopefully that should work as well.
Updating to 1.5.2 from 1.5.1 does indeed prevent the error due to the new chunkLoading
check.
Technically a configuration with chunkLoading: false
& target: ['web', 'es5']
would trigger the warning but that is probably not common enough to special case.
Thank you for the quick response.
Current Behavior:
When using Webpack 5, the Webpack
target
option can also be an array of strings (documentation). When this form of the option is used, this plugin will issue a warning even ifweb
is present in thetarget
option array.Expected Behavior:
When the
target
option is an array and the array contains aweb
element, this plugin should not emit a warning.Additional Notes:
For advanced use cases, the
target
option can also befalse
(documentation). In this case it allows the user to manually configure target plugins which may include web capabilities. With a value offalse
, the warning from this plugin may also be considered incorrect in such situations.