fix: exports and imports array target resolving

[alexander-akait]

fixes #400

[hardfist]

@alexander-akait does this deprecate https://webpack.js.org/guides/package-exports/#alternatives behavior? will this be shipped in webpack@5?

[alexander-akait]

@hardfist we should rewrite our docs because we are align with Node.js behaviour right now

[alexander-akait]

webpack/webpack.js.org#7323

[hardfist]

@hardfist we should rewrite our docs because we are align with Node.js behaviour right now

@alexander-akait one of our internal webpack projects break because of this change, I'm not sure whether should provide a option to change this behavior would be better, but it's indeed a breaking change and change the default value in next big version seems better?

[alexander-akait]

@hardfist Technically you are right, but I would say it is better to fix it in the project, because relying on behavior that was initially designed incorrectly is not the best idea, most likely it would break in other bundlers and in the node itself, as workarund you can fix old version or just copy paste our old code (as a plugin) and set other stage