.nodemonwatch file

[remy]

@PhUU (and a little bit me) requests the inverse of the .nodemonignore file.

The ignore file would take presidence, but if the watch file was there, you wouldn't have to have complicated rules on the command line all the time.

[tgvashworth]

Or just some way to configure nodemon more specifically, like a json file.

[jcblw]

I would love this but I kinda cringe at adding another dotfile in the root of my projects. I like json @PhUU then you could eventually have .nodemonignore migrate to that file as well.

This is kinda what Im envisioning
https://gist.github.com/jacoblwe20/5279908

[remy]

@jacoblwe20 yeah, I'm not keen on adding another file either. I think some kind of automatic detection for a new format of ignore file might be on the books.

[G3z]

👍 for @jacoblwe20 's JSON

[vjpr]

+1

[leostera]

👍

[pasindud]

It would be easy if it is JSON

[pasindud]

https://github.com/pasindud/nodemon/commit/5f863ddda2a99f83b702d80cab0946918987f5bc

I did this few minutes ago which enables you to use a nodemon.json file to include ignore files, not sure whether it is correct but it works.@remy wht do u think about this?

[remy]

I will be implementing this, but giving a lot more control to the json file - rather than just another format for ignoring.

[remy]

Very much along the lines of @jacoblwe20's gist.

[anotheri]

+1 for config file (.json) for nodemon

[pasindud]

pull #183 i think @remy is working on adding the watch implementation

[remy]

That's right, I'm dedicating time to the work this week (starting Tuesday
if all goes to plan).

On 21 July 2013 19:29, Pasindu De Silva [email protected] wrote:

pull #183 #183 i think @remyhttps://github.com/remyis working on adding the watch implementation

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/155#issuecomment-21314474
.

[remy]

My feeling is the .json should be a dotfile - only because it's the kind of thing you probably don't want in your github repos.

Agree? Disagree? Please say why.

[dogancelik]

I think every project should have its own config file ./nodemon.json (per project config file) and a global config file ~/.nodemon.json. I don't mind having a nodemon.json in my repo.

A per-project config file could look like this:

{
  "ignore": [
    ":/.*\\.(js|coffee)",
    "/public/*",
    "/vendor/**.js"
  ]
}

And a global config file could look like this:

{
  "ignore": [
    "/.git/*"
    "README*",
    "LICENSE"
  ]
}

[jcblw]

I have to say that I usually have the .nodemonignore file in my repo's if im using it. Especially when working on a collaborative project with a team that is all using nodemon, and I think you would still need to specify that you wouldn't want to track .nodemonignore file.

[remy]

No longer needed, v1.x uses a nodemon.json config file with lots of control now.