Fix types for Config.resolve plugins and improve Plugin types

[opl-]

• Fixes Config.resolve.plugin call expecting a webpack.Plugin type despite those plugins being passed an enhanced-resolve/lib/Resolver argument type. (As seen in this test which uses it as a resolve plugin)

  • All added generics default to webpack.Plugin in order to stay fully backwards compatible with previous versions.

• Allows passing string to Plugin.use() as those get required by webpack-chain here.

• Allows passing PluginType to Plugin.use() and Plugin.init() as the default implementation allows it.

• Adds tests for the changes.

  • To make that possible, @types/enhanced-resolve and @types/tapable were added to devDependencies to allow the tests to work.

  • The webpack.ResolvePlugin type currently uses any as the apply() argument type. The tests use the Resolver type to future-proof.

    • As it turns out the reason is that the DefinitelyTyped enhanced-resolve types are a major behind, so the DefinitelyTyped types for webpack simply don't reference them. They can't be reused either, as enhanced-resolve v3 uses tapable v0 while enhanced-resolve v4 uses tapable v1. See enhanced-resolve types for v4 are missing DefinitelyTyped/DefinitelyTyped#40804

    • Meanwhile, the official webpack types are also invalid. I created an issue on the official webpack repo to track that: Type definitions use normal webpack plugin types for resolve.plugins webpack/webpack#10073.

[opl-]

Force push because I didn't notice the yarn.lock and assumed packages aren't locked.

[edmorley]

Sorry for the delay in replying - thank you so much for fixing these! :-)

[edmorley]

Published in v6.1.0 :-)