Using components to register the module is a really ugly workaround to my mind. I'd like to see this soon, I can imagine this causes headaches for extension developers that first have to do with modules.
similar or same bug 459107 which has a different workaround. I don't think that is the right fix, since it means any extension needing to have modules will need to replicate that code. This should be handled on extension load, since the module directory is specified in chrome.manifest.
You need to log in before you can comment on or make changes to this bug.