Great. 💃

I'd suggest the webpack entry in package.json would point to ./lib/index.js instead. When pointing to dist webpack produces this warning:

WARNING in ./~/plotly.js/dist/plotly.js Critical dependencies: 7:479-486 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. @ ./~/plotly.js/dist/plotly.js 7:479-486

The issue with pointing at the ./lib/index.js is that we use the Browserify "glslify" transform to work on our gl components, so webpack users would have to use a more complex setup involving either transform-loader, or ify-loader (I had more success testing with ify-loader).

The reason we left webpack pointing to the built file is that it doesn't really matter. The output of webpack is seldom looked at, and typically will be minified anyways.

@fhurta good point. But, I'm not convinced making lib/index.js the webpack entry point would be better as it would require webpack users to add the ify-loader to their config (more info here).

So, what's better for the main webpack entry point? Webpack spitting out warnings or making users require some third-party module in order to bundle properly?

OK, then. Thanks for response.
However, FYI, I use webpack (1.13.1) and have nor transform-loader neither ify-loader installed and import (typescript's require) from lib.

Yep! That's precisely why we didn't point the webpack entry to the lib/index.js!

By using the built bundle, webpack users aren't required to have any extra dependencies. The browserify transforms do their thing on our end at build time when we create the file at dist/plotly.js.