Open nishantkagrawal opened 7 years ago
Do you have any temporary workaround for this?
Hi @nishantkagrawal, sorry but I haven't used myself this plugin with bower. Are you using AMD?
@rxaviers, Yes I am using AMD.
Yes I am using AMD.
Interesting...
Globalize itself indeed supports either CommonJS or AMD, but this webpack plugin only supports CommonJS (for history/context, please see https://github.com/globalizejs/globalize/issues/441). Therefore, this plugin deliberatively disables the AMD portion of Globalize UMD wrapper (dev code prod code).
If you have a better idea to make this plugin work smoothly by CJS and AMD users, feel free to submit your thoughts and a PR.
Thank you
@rxaviers I am having issues with bower-resolve-webpack-plugin and globalize-plugin to work together.
If I install gloablize in node_modules it works fine. But globalize-webpack-plugin doesn't pickup the globalize module from bower_components.
Note that all my other modules are loaded from bower_components using bower-resolve-webpack-plugin.
bower-resolve-plugin is using existing-directory plugin to process all the stuff. When webpack hits globalize, it ignores that plugin somehow.
The following is my configuration.
The following is the error:
Am I missing a sequence in which the plugins should be setup or anything else?
The basic repo to reproduce this problem is here