Mismatch between AMD and CommonJS module definition in UMD module

While working on converting a project to webpack from browserify, I ran into an issue with one of the project’s dependencies. The dependency hashmap is written as a UMD module, but the shape of the AMD module and the CommonJS module are different. Webpack favors the AMD definition, which caused an issue when compiling via webpack.

The issue is demonstrated in gcorne@4f115d8

My expectation coming from a node/commonjs mindset is that commonjs would be given a higher priority when parsing a UMD module or that there would be some configuration option to favor using the commonjs version over amd to allow for better compatibility with 3rd-party npm libraries.

Author: Fantashit

2 thoughts on “Mismatch between AMD and CommonJS module definition in UMD module

Comments are closed.