Grunt watch task not detecting new directories inside /client/components/

[eemelisoderholm]

For some reason the grunt watch task does not detect new directories and their files inside /components/. Grunt serve has to be restarted every time a new component is added, which is a minor inconvenience.

I'm not sure what is causing this, as new directories under /app/ are detected and processed normally, yet they both share the same node-glob strings like '<%= yeoman.client %>/{app,components}/*/.{scss,sass}'

Easiest way to test this is to make a copy of an existing directory. I'd expect it to work inside /components/ the same way it does inside /app/.

Tested in 64bit Windows 7, node 0.10.26, npm 1.4.3.

[kingcody]

I can confirm this issue. Have been experiencing it for some time now.

[kingcody]

See grunt-contrib-watch #166

[kingcody]

Also for fun, try rewriting the glob patterns like so:

'<%= yeoman.client %>/{components,app}/**/*.{scss,sass}'

and run your tests again.

[kingcody]

Either way, the basic gist of 166 is to TRY adding:

options: {
  cwd: process.env.PWD
}

to your individual watch configs

It seems to work for me, still doesn't seem to address the root issue; but I guess thats with gaze.

[kingcody]

@voidsheep it appears I spoke to soon. I was not able to resolve the issue. My apologies, I'll be sure to let you know if I do find something.

[DaftMonk]

Try swapping out the injector b0ce36e

My forked changes got merged upstream, and there's been some updates to the injector that have fixed similar issues I was having.