Adrian Rakovsky

If anyone interested, I have succeed in creating custom callHandler for UMD: ``` define([ "dojo/_base/lang", "dojo/AdapterRegistry", "jsdocparser/lib/env", "jsdocparser/lib/callHandler/amd", "jsdocparser/lib/console" ], function(lang, AdapterRegistry, env, amd, console) { var handlers = new...

Your (s)query is (wrongly??) interpreted as compound attribute. That's why it does not match. See the docs https://www.graspjs.com/docs/squery/. > If you want to only match primitive attributes, you can add...

Flow parser is OK. Error occures in `grasp-squery/lib/common.js#17` (`property.key` is `undefined`) See screenshot from debugger 

I have one more commit, which I haven't include in any PR https://github.com/gratex/grasp/commit/54d889a654f7b9318d7279ba6 It was just a quick workaround, not widly tested. Take a look at if if you want...

When will be this merged in? We are waiting for weeks to start using it.

+1, I'm facing the same issue

Well, I have probably found the issue: my code does not (yet) contain any formatters; code like this one: ``` Globalize.formatMessage("intro-1")() ``` (which is corresponding to the error message 'No...

But when I check the output in 'release' mode, maybe this plugin is not suitable for usage with react-globalize, because only those messages get to 'globalize-compiled-data', which are used directly...

I have end up with the same issue when I use yours `react-globalize-webpack-plugin` set `writeMessages: true`, and there is no call for `Globalize.formatMessage`. What I really want to do, is...

+1