Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[bug] 1.4.0 introduces "global is not defined" #218
As of 1.4.0, Webpack no longer is polyfilling
I believe the issue was introduced here: #216
A workaround for now:
The problem is that doing a major doesn't really help you. Only one copy of ember-auto-import is allowed to win, and if the app has one, it will be that one. So as soon as apps upgrade, ember-intl would break again in the same way.
I do consider #216 a bugfix. Automatically polyfilling node behaviors for the browser was never intentional.
I agree that the situation with webpack configs is not ideal. Unfortunately they don't compose well, and most settings are extremely global in nature. So it's hard for addons to change settings without having big side effects. But that is why I think it's so important to have defaults that try to adhere as closely as possible to web standards, without sneaking in implementation-defined things like webpack's polyfills.