We should pull out those hard-codings, make them part of a configurable plug-in system, and make it part of the general push to modularize the build system. E.g. if the build system becomes a WinningJS-build npm package, the Jade compilation could become separate enough to be a WinningJS-build-jade package.
This is kind of done with the existence of https://github.com/NobleJS/WinningJS-todo/blob/45b8588b0a4c9632a57a7633a4e093d27630cddd/build/browserifyHandlers.js. But then again, we hard-code the bundling and auto-execution of the Jade runtime.
We should pull out those hard-codings, make them part of a configurable plug-in system, and make it part of the general push to modularize the build system. E.g. if the build system becomes a
WinningJS-buildnpm package, the Jade compilation could become separate enough to be aWinningJS-build-jadepackage.