We should throw an error when a module is required that can't be loaded because it doesn't exist. Seems reasonable, eh?
Don't need this test anymore, since the widget V2 test subsumes this.
Introduction should be sorted at the top.
The section titles are "Static Methods" and "Static Properties". "Public" is redundant and causes more sections to appear in the docs, because the stitched in feature information goes into "Static Methods" and such.
A hack to not build the ~experimental JS modules until I figure out something better to do with them. Since I enabled error throwing in build.js not being able to load modules, these have been causing problems in the build process.
Add support for JS modules built from .css.source files.