`grow run` does not watch for changes in included files any longer

Heya!

I noticed recently that Grow doesn’t pick up changes to included files anymore, so if you, like me, inline a CSS file in a partial, like so:

{% include "/assets/css/main.min.css" %}

then make changes to that file and reload the page, these changes are not picked up. I have to kill the process and restart, which defeats the purpose of the grow run mode. This has worked before – any possibility to bring it back, or any potential workaround?

Thanks!

[Zoramite]

@matthiasrohmer I think that you may have hit this on the head when you talked about gulp not picking up the changes.

In the later versions of gulp the changes were not updating the mtime of the file in the later versions of gulp which was throughing off grow’s file watchers. I think that some of the changes that we did should work around the mtime issues completely, but let me know if you are still seeing issues.

See: https://github.com/grow/grow/issues/955

[pbakaus]

Hi again, sorry for the incredible delay!

I confirmed that even with a full build (grow build), sass changes are not picked up in my local build when in grow run mode.

I did the following:

1. grow run
2. Open _mission.scss
3. Browse to http://localhost:8080/about/mission/
4. Change line 35 in _mission.scss from background: white to background: red
5. Observe in terminal that sass task ran successfully and picked up the changes
6. Reload browser window
7. No changes are picked up, even though the generated mission.min.css picked it up, and is imported in the head of the page

Help?

(We confirmed this on several machines)