After update to 1.4.1 nodemon is not starting any longer node ./bin/www

[TheFive]

I just use the standard generated app with the npm start script:

"start": "NODE_ENV=development node ./bin/www"

This was no problem in 1.4.0, but now i got the error:

----% nodemon
29 Aug 21:05:08 - [nodemon] v1.4.1
29 Aug 21:05:08 - [nodemon] to restart at any time, enter rs
29 Aug 21:05:08 - [nodemon] watching: .
29 Aug 21:05:08 - [nodemon] starting NODE_ENV=development "node ./bin/www"
sh: node ./bin/www: No such file or directory
util.error: Use console.error instead
[nodemon] failed to start process, "NODE_ENV=development" exec not found

node ./bin/www runs fine out of the directory where i start nodemon from.

The version 1.4.0 forces me to update, so i can't use nodemon yet :-(

Christoph

[remy]

What version were you on before?

[TheFive]

Hi Remy,
i have installed a backup, it was the version 1.4.0. But "o wonder" with the backup i get the same problem. (and no update force yet).

[TheFive]

If I change
"start": "NODE_ENV=development node ./bin/www"

to

"start": "node ./bin/www"

it works, so may be there is a change in the background that causes the error.

As a workaround i have created a start script, setting the environment variable and starting ./bin/www.

May be it is a problem in my development configuration, and it is caused because i installed xcode terminal apps ?.

I am working on Yosemite 10.10.5 (all updates til now).
As i have a workaround, you can close the issue, if you want.

Christoph

[remy]

Can you test it with npm install -g nodemon@1.3 ?

On Sun, 30 Aug 2015 09:24 TheFive notifications@github.com wrote:

If I change
"start": "NODE_ENV=development node ./bin/www"

to

"start": "node ./bin/www"

it works, so may be there is a change in the background that causes the
error.

As a workaround i have created a start script, setting the environment
variable and starting ./bin/www.

May be it is a problem in my development configuration, and it is caused
because i installed xcode terminal apps ?.

I am working on Yosemite 10.10.5 (all updates til now).
As i have a workaround, you can close the issue, if you want.

Christoph

—
Reply to this email directly or view it on GitHub
#621 (comment).

[TheFive]

Hi Remy,

here the result.

30 Aug 13:01:31 - [nodemon] v1.3.8
30 Aug 13:01:31 - [nodemon] to restart at any time, enter `rs`
30 Aug 13:01:31 - [nodemon] watching: *.*
30 Aug 13:01:31 - [nodemon] starting `NODE_ENV=development "node ./bin/www"`
sh: node ./bin/www: No such file or directory
util.error: Use console.error instead
[nodemon] failed to start process, "NODE_ENV=development" exec not found
exception in nodemon killing node

[remy]

So looks like its been like this for a while.

On Sun, 30 Aug 2015 12:03 TheFive notifications@github.com wrote:

Hi Remy,

here the result.

30 Aug 13:01:31 - [nodemon] v1.3.8
30 Aug 13:01:31 - [nodemon] to restart at any time, enter rs
30 Aug 13:01:31 - [nodemon] watching: .
30 Aug 13:01:31 - [nodemon] starting NODE_ENV=development "node ./bin/www"
sh: node ./bin/www: No such file or directory
util.error: Use console.error instead
[nodemon] failed to start process, "NODE_ENV=development" exec not found
exception in nodemon killing node

—
Reply to this email directly or view it on GitHub
#621 (comment).

[TheFive]

Just for your information...

-----------------------------------------
Update available: 1.4.1 (current: 1.3.8)
Run npm update -g nodemon to update
-----------------------------------------
30 Aug 13:36:01 - [nodemon] v1.2.1
30 Aug 13:36:01 - [nodemon] to restart at any time, enter `rs`
30 Aug 13:36:01 - [nodemon] watching: *.*
30 Aug 13:36:01 - [nodemon] starting `NODE_ENV=development node ./bin/www`
util.error: Use console.error instead
[nodemon] unable to run executable: "NODE_ENV=development"


30 Aug 13:37:08 - [nodemon] v1.1.1
30 Aug 13:37:08 - [nodemon] to restart at any time, enter `rs`
30 Aug 13:37:08 - [nodemon] watching: *.*
30 Aug 13:37:08 - [nodemon] starting `NODE_ENV=development node ./bin/www`
util.error: Use console.error instead
[nodemon] unable to run executable: "NODE_ENV=development"

[nicothed]

I had the same issue: 1.4.0 was working fine, but after updating, when a file changed, it displayed:
7 Sep 13:45:40 - [nodemon] restarting due to changes...
but didn't restart anything! :(

I reverted to v1.3.0, 1.4.0 and back to 1.4.1 but it was all the same behavior.

I have somewhat fixed it by adding which file to run (server.js). It works sometimes, but not always.. quite frustrating as I always have to check the console time to make sure the code ran :(

[alberto-f]

Hey, I just tried version 1.7.0 and while it detects when Im updating the files the browser its not updated. Pretty much as the prev. issues were saying. Was it fixed?

[remy]

@alberto-f "the browser is not updated" - ? Updating the browser isn't part of nodemon. I suspect you're confusing this with something like live-reload...?