Fixed by https://github.com/Polymer/platform-dev/commit/1f7ae77762cd287d7893c00eecc000ad8acebd47#diff-47426efabbdf4a14eefdc36d3a774fc0 , thanks a lot !
Le jeudi 8 mai 2014 14:26:01 UTC+2, R. LANG a écrit : > > Hi, > > I'm trying to integrate polymer in an existing application and encountered > an issue with the global 'module' method exported by > https://github.com/Polymer/platform-dev/blob/master/src/module.js > <https://github.com/Polymer/platform-dev/blob/master/src/module.js> > > Some of my external libs provides support for both nodejs modules and AMD > using a pattern like : > > (function (name, definition) { > if (typeof module != 'undefined') module.exports = definition() > else if (typeof define == 'function' && typeof define.amd == 'object') > define(name, definition) > else this[name] = definition() > }( //... > > > > I will submit pull request to these libs to use a more robust check > <https://github.com/umdjs/umd/blob/master/nodeAdapter.js> so they can > work with Polymer, but isn't a global 'module' method prone to conflict > with other existing library ? > Should I open an issue, or is it mean to stay this way and my other libs > to improve their nodejs module detection pattern ? > > > Best regards, > R. LANG. > > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/62b1a1c3-2253-471f-86ec-7bc9c6aa92ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
