Add support to pipe console output from express to the grunt console for debugging? about grunt-express-server HOT 7 CLOSED

Nevermind, this is already the case. I had a typo. Sorry!

from grunt-express-server.

:) MAGIC!

from grunt-express-server.

Sorry dude, it's been a LONG week. But great little project here! I had a crazy setup with grunt-concurrent and grunt-watch and grunt-nodemon to pretty much do the same thing...

from grunt-express-server.

Hey no worries. I'm constantly having long weeks, and my open-source projects end up getting hurt. I'll have to take some vacation to enjoy these guys again & make their Gulp.js equivalent.

from grunt-express-server.

Everyone keeps switching to Gulp everywhere I go... Why the sudden rush to jump ship?

from grunt-express-server.

Well, I never liked Grunt's architecture, in the same way that I don't like WordPress'.

Having written several plugins, I absolutely hate the loose way that plugins accept configurations. I prefer a very specific, programmatic API over having to make lots of separate configs to make tasks play nice.

As an example, I have a project (which hasn't been touched in 7 months) where I finally brought some order to the whole Express + Angular + Grunt thing:

https://github.com/ericclemmons/genesis-skeleton/blob/master/Gruntfile.coffee

It took a lot of trial-and-error to get watching, livereloading, and tasks all playing nice. (For example, you don't want to reload the express server just because you changed some stylesheet.)

I'm entertaining Gulp.js, because it's closer to how I think a build system should operate (a Node version of Make) instead of a complex configuration file.

from grunt-express-server.

Interesting.. I'll have to take a closer look. I just wrangled my gruntfile
as well to handle backbone/minification/EJS/express/css/express/etc. Once
it works, though, it's a beautiful thing! I'd hate to have to learn a new
build process, but I'll definitely take a look at Gulp!

from grunt-express-server.