No compass files or grunt task when generating a client only app.

[juliomenendez]

If you select "No" to the server app questions like this:

[?] Would you like to install the full express app or simply the marionette generators? No
[?] Would you like to include MongoDB for storage? No
[?] Would you like to include Socket IO for real time communication? No
[?] Would you like to include Baucis for REST? No

this is the project structure created:

total 40
-rw-r--r--   1 julio  staff  7291 Jul 31 14:52 Gruntfile.js
-rw-r--r--   1 julio  staff   563 Jul 24 08:13 bower.json
drwxr-xr-x  19 julio  staff   646 Jul 31 14:52 bower_components
-rw-r--r--   1 julio  staff  1225 Jul 31 14:52 index.html
drwxr-xr-x  28 julio  staff   952 Jul 31 14:52 node_modules
-rw-r--r--   1 julio  staff   959 Jul 31 14:52 package.json
drwxr-xr-x   8 julio  staff   272 Jul 31 14:52 scripts
drwxr-xr-x   3 julio  staff   102 Jul 31 14:52 templates
drwxr-xr-x   5 julio  staff   170 Jul 31 14:52 test

As you can see there isn't a styles folder nor compass grunt task so it doesn't work:

Running "createDefaultTemplate" task

Running "handlebars:compile" (handlebars) task
>> Destination not written because compiled files were empty.

Running "compass:dist" (compass) task
Verifying property compass.dist exists in config...ERROR
>> Unable to process task.
Warning: Required config property "compass.dist" missing. Use --force to continue.

Aborted due to warnings.

[mrichard]

Hi,

The goal of the no express app option was to only have the JavaScript functionality with a minimal way to run the default grunt task. I often come across projects where I have to build a mini SPA within the larger project. In these cases the CSS (SASS) is done elsewhere and I just want the marionette generator functionality with unit testing. Let me know what you think. This could be open for discussion.

I wil eventually clean up any grunt tasks that shouldn't be there. This again is partly due to the grunt file not being completely finished.

Thanks

[juliomenendez]

Hmm, I think the purpose for the no express app should still give you a working web app, that is with HTML, JS and CSS (SASS). I think an only JS option is not really usable.

I’m looking at this from this 2 points of view:

1- Client/server on the same project with JS. 2- Client on this project with JS. Server on another project with Ruby/Python/PHP/your own lang.

In both cases this generator should give me a working client app with all a web app needs, right?

Julio Menendez LLC Software design and development done right (801) 747-9480 | [email protected]

On Thursday, August 1, 2013 at 3:55 PM, Michel Richard wrote:

Hi, The goal of the no express app option was to only have the JavaScript functionality with a minimal way to run the default grunt task. I often come across projects where I have to build a mini SPA within the larger project. In these cases the CSS (SASS) is done elsewhere and I just want the marionette generator functionality with unit testing. Let me know what you think. This could be open for discussion.
Thanks

— Reply to this email directly or view it on GitHub (https://github.com/mrichard/generator-marionette/issues/5#issuecomment-21972735).

[mrichard]

Yeah I mean you get HTML and JS, just no CSS/SASS. I guess that is a specific use case to me. Maybe we can prompt for CSS/SASS folders to be included? So users can opt in or out in both application types.

[juliomenendez]

Yeah, that should work too. That option needs to enable/disable the compass tasks in grunt as well. What about keeping the app folder when the user says no to the express server?

Julio Menendez LLC Software design and development done right (801) 747-9480 | [email protected]

On Thursday, August 1, 2013 at 4:06 PM, Michel Richard wrote:

Yeah I mean you get HTML and JS, just no CSS/SASS. I guess that is a specific use case to me. Maybe we can prompt for CSS/SASS folders to be included? So users can opt in or out in both application types.

— Reply to this email directly or view it on GitHub (https://github.com/mrichard/generator-marionette/issues/5#issuecomment-21973401).

[Freddy03h]

I'm agree to keeping the app folder even if we don't want express

[juliomenendez]

@mrichard what do you think of making this change?

[jrmlstf]

It would be really great to keep the app folder and SASS support in non-express mode.

[sprugman]

Another vote for sass support without express.

[omasback]

I agree. the question makes it seem like answering no wouldstill set up a full front-end scaffold with compass and working grunt build, only minus all the backend stuff. And that is what I would like it to do.