Modules export minified code

The UMD modules available in npm export minified code. While this does not stop us using these modules, it throws warnings in our Webpack dev server. Since these are source modules would it make more sense to export them un-minified and leave the end user to handle minification?

Example of console warning:

./~/braintree-web/client.js
Critical dependencies:
1:438-445 This seems to be a pre-built javascript file. Though this is possible, it's not recommended. Try to require the original source to get better results.
@ ./~/braintree-web/client.js 1:438-445

[crookedneighbor]

The problem is not that it’s minified, but that it is pre-built using Browserify. If you use the the debug versions of the files which are not minified (like require('braintree-web/client.debug')), you’ll get the same error because they are still bundled beforehand.

We’re discussing how we can support Webpack without displaying these errors, but it requires us to change how we distribute the files and we want to make sure we don’t break anyone who is already using the package. For example, if someone is downloading the module through npm and then copying the files from the node_modules folder directly to their frontend, providing pre-built files would break their integration as soon as they upgraded to a new minor version.

[mrak]

Thanks for the detailed response, @M-Porter. You are absolutely correct; we overlooked our index.js and debug.js files which still had references to require.

We have just released version 3.3.0 where these two files are correctly bundled without references to require.