Closed adamhooper closed 8 years ago
Compilation of the majority of the JS ecosystem requires browserify and/or webpack - that's the nature of JS in 2016.
It is a hugely best practice to require consumers use browserify/webpack/etc, and a very bad idea to enable people to hurt themselves by not using it, by providing them with workarounds.
In other words, a "non-Browserify/Webpack environment" is obsolete, and is best served by becoming one.
I tried using Polyglot in a non-Browserify/Webpack environment. I ran into the following problems:
Since each function serves a tiny purpose, I worked around those problems in https://github.com/adamhooper/polyglot.js/tree/for-decision-2016. Surely I'm not the only one who experiences these problems. Would you consider a pull request?