search

dbashford / mimosa-client-jade-static

A mimosa module to use jade to create HTML client templates
2 stars 4 forks source link

Module no longer working #6

Closed neverfox closed 10 years ago

neverfox commented 10 years ago

I was recently converting a project to client static Jade and none of my files were ending up in public, with no warnings or errors. So I tested out a new project as follows, with Mimosa 2.1.19:

  1. mimosa new jade-test
  2. Select: 3, 4, 9, 2, 1
  3. Add client-jade-static to modules in config
  4. Add file assets/javascripts/app/test.html.jade (with or without content, doesn't matter)
  5. mimosa watch -s
  6. No test.html is found in public/javascripts/app or anywhere

Here is the --mdebug output that mentions the file (and a few extra lines for context):

00:25:33 - Info - Module mimosa-client-jade-static cannot be found, attempting to install it from NPM into your project.
mimosa-client-jade-static@0.7.1 node_modules/mimosa-client-jade-static
00:25:34 - Success - mimosa-client-jade-static successfully installed into your project.
...
00:25:36 - Debug - File assets/javascripts/app/example-view.iced NEEDS compiling/copying
00:25:36 - Debug - Finished with file assets/javascripts/app/test.html.jade
00:25:36 - Debug - Calling compiler function for compiler iced

I tried this on both Linux and Windows to no avail.

dbashford commented 10 years ago

I'll have to get back to this this weekend/next week. On work travel and won't have any time to play around. I apologize!

neverfox commented 10 years ago

No problem. I'm currently using this as a (less-than-ideal) stopgap.

dbashford commented 10 years ago

Have to add jade, the compiler, to the modules list. I updated the docs awhile ago for that.

Before, when all the compilers were built in, that obviously wasn't needed. But this module depends on the work that the template compiler performs.

This module probably needs to be properly detached now from template compiling.

neverfox commented 10 years ago

Ah geez, I saw that but somehow interpreted it as referring to a node module. Sorry about that. Still adjusting to the move from 1.x but I think I'm there now.