gulp serve broken out of the box with CSS option

[ggallo]

Item	Version
generator-angular-fullstack	3.3.0
Node	5.3.0
npm	3.8.5
yo	1.7.0
Operating System	OS X 10

Item	Answer
Transpiler	Babel
Markup	HTML
CSS	CSS
Router	ui-router
Build Tool	Gulp
Client Tests	Mocha
DB	MongoDB
Auth	Y

To recreate:

1. yo angular-fullstack with the options above
2. gulp serve and you receive this error: Error: Task inject:css is listed more than once. This is probably a typo. Easily fixable, I suspect the second inject:css is meant as a placeholder in case a preprocessor was selected in step 1
3. Run gulp serve after removing the duplicate command, and localhost:9000 is clearly missing style resources. I suspect that bootstrap and font awesome are not being loaded.

If you generate a second app that's exactly the same, except you select Less as a preprocessor, gulp serve works out of the box, and the demo app appears as expected. (This may hold for other preprocessors, I didn't check.) Could be related to #1466 and #1752

[Awk34]

Try the latest version of the generator

[ggallo]

Oops, didn't catch that. But still the same problem with [email protected] after following the exact same steps.

I think it's because with the preprocessor, you get bootstrap and font awesome injected into client/app/app.less, but not with CSS. Just a guess, I'm a bit 🆕 to this stuff.

Here's a reference image for what I'm seeing with CSS:

And again, using Less looks great:

[ggallo]

In fact, the inject:css task seems completely broken across all preprocessor options. Run a gulp serve and in client/index.js, there's nothing inside the injector:css tags. Compare that to the injector:js tags, which contain the necessary scrips after the task.

[dsschnau]

Hey, just another data point for this issue:

I set up an app to use css (no sass/less/styl), and there was indeed a gulp task that did inject:css twice which caused the error in this report. I didn't look further but I guessed that one of the inject:css tasks would have been for a css preprocessor. I deleted it and moved on but just wanted to let y'all know.

[Awk34]

I believe this has been fixed