This problem is caused due to a name collision between the module itself and the type. We have a bunch of bug reports related to this... There's a temporary workaround for this (use the `-Xfrontend -module-interface-preserve-types-as-written`) flag if you really need to use it but the best way forward is to rename the type to avoid the name collision with the module.
This is a special case of SR-898 occurring in a module interface file. When a visible type has the same name as a module, the type shadows the module and there is currently no syntax to get around that.
Fixing this properly will require a language change like the module selectors pitch. We think it's a good idea, but we haven't found the time to do it yet.
Until we have something like that, Varun's suggested workarounds are good ones.