Nested module names aren't supported

[lukewestby]

Currently one can customize the module name used by elm-css with the --module=Whatever option. The value passed in is used as a single string and a check is performed to look up the module name on the top-level Elm object:

var worker = Elm[stylesheetsModule].worker();

This means that any module name with nested qualifiers will fail. For example, trying to pass Apps.Editor.Stylesheets will result in

Error: I couldn't find the entry module Apps.Editor.Stylesheets.

Maybe you meant: Apps
You can pass me a different module to use with --module=<moduleName>

due to these lines:

if (!(stylesheetsModule in Elm)){
  return reject(missingEntryModuleMessage(stylesheetsModule, Elm));
}

A potential fix would have to walk the module name hierarchy both when looking up the module to create the worker and in the suggestModulesNames function for printing available modules when the module given truly isn't there