Shouldn't the browser page reload when I edit and save any of the files in the app folder, as is the case when using connect::livereload? As far as I can tell, nothing happens. I have to manually reload the browser page to see the change. Is this as expected?

When you execute grunt server:dist you can see that after the build occurs that the express:dist:keepalive task is run, but the server does not stay open and grunt exits .

Console Output:

Running "open:server" (open) task

Running "express:dist:keepalive" (express) task

Running "express-server:dist" (express-server) task
Web server started on port:9000, no hostname specified [pid: 45270]

Done, without errors.

I just cloned the project and followed your directions and I get the following error when I run "grunt server"

    error app/styles/main.scss (Line 247 of app/bower_components/bootstrap-sass/lib/_mixins.scss: Invalid CSS after "...-shadow($shadow": expected ")", was "...) {")

Hi,

I have the following setup:

express: {
dev: {
options: {
hostname: "localhost",
server: path.resolve(__dirname, 'app.js'),
// serverreload: true
}
}

Whenever I modify some files this is what I get:

Running "express-server:dev" (express-server) task
app.js
Port 3000 in use
Web server started on port:3001, hostname: localhost [pid: 18494]

And I don't see the changes that I'm making in the server side js files.

If I set serverreload: true, I get the following result but I still don't see the changes made in the server side js files:

Running "express-server:dev:/tmp/express116316-18541-1ac0ya5/dev.server" (express-server) task
app.js
Web server started on port:3000, hostname: localhost [pid: 18550]

What am I doing wrong ?

Thanks in advance.

Have these examples in the README.md actually been tested lately, they dont work in Node and Express with the latest versions?

After starting this project, I ran

npm install
bower install
grunt test

Returns the following error:

Chrome 29.0 (Mac) Controller: MainCtrl should attach a list of awesomeThings to the scope FAILED
    Error: No module: ui.bootstrap
        at Error (<anonymous>)
        at /Users/mpwd/Development/mao/app/bower_components/angular-unstable/angular.js:1148:17
        at ensure (/Users/mpwd/Development/mao/app/bower_components/angular-unstable/angular.js:1089:38)
        at module (/Users/mpwd/Development/mao/app/bower_components/angular-unstable/angular.js:1146:14)
        at /Users/mpwd/Development/mao/app/bower_components/angular-unstable/angular.js:2837:24
        at Array.forEach (native)
        at forEach (/Users/mpwd/Development/mao/app/bower_components/angular-unstable/angular.js:148:11)
        at loadModules (/Users/mpwd/Development/mao/app/bower_components/angular-unstable/angular.js:2833:5)
        at /Users/mpwd/Development/mao/app/bower_components/angular-unstable/angular.js:2838:38
        at Array.forEach (native)
    TypeError: Cannot read property 'awesomeThings' of undefined
        at null.<anonymous> (/Users/mpwd/Development/mao/test/spec/controllers/main.js:20:17)
Chrome 29.0 (Mac): Executed 2 of 2 (2 FAILED) (0.162 secs / 0.039 secs)
Warning: Task "karma:unit" failed. Use --force to continue.

Aborted due to warnings.

Turning on HTML 5 mode via $locationProvider.html5Mode(true); in the app.js causes Angular routes to be completely unavailable.

Is there a work around for this?

I cloned this repo, and am running grunt with the configurations provided. Whenever I try to make a change to files that are meant to be watched (in this case, app/styles/main.scss) the files do not update properly. I think the server process is blocking the watch processes for some reason. When I run grunt watch the static files update as expected.