feat: Mark Webpack 5 as supported (#216)

[denis-sokolov]

This PR contains:

• bugfix
• feature
• refactor
• tests
• documentation
• metadata

Breaking Changes?

• yes
• no

Please Describe Your Changes

Default Webpack version is now 5, discussed in #216.

Although considering the readme of this project suggests webpack-nano, perhaps a better option is to remove the peer dependency altogether.

[shellscape]

folks, while I appreciate the contributions and the interest in the project, I really need everybody to start searching issues before opening new ones. I have addressed this several times and have stated several times that I will switch to webpack 5 for this project when I feel that the time is right. thanks again, but I cannot accept your pull request at this time

[denis-sokolov]

Sincere apologies. I’ve assumed that since the issue above (#216) is open and mentioned Webpack 5 as working fine, I’d reduce the friction to integrate it.

Perhaps keeping a Webpack 5 issue like #195 open would help? From the point of view of consumers missing Webpack 5 support is an outstanding concern that, and an open issue communicates it very clearly.