Menu icon Foundation
Project not rebuild/update after changes have been made

When I modify the scss files, or the partials, or the layout, or the pages files,... I expect to see the changes automatically in the browser, but this is not what's happening. After starting the project and run the watch target, it does nothing when I modify the files.

[17:44:01] Requiring external module babel-register

[17:44:14] Using gulpfile /mnt/hgfs/koala/emails/KoalaEmails2/gulpfile.babel.js

[17:44:14] Starting 'default'...

[17:44:14] Starting 'build'...

[17:44:14] Starting 'clean'...

[17:44:14] Finished 'clean' after 13 ms

[17:44:14] Starting 'pages'...

[17:44:14] Finished 'pages' after 509 ms

[17:44:14] Starting 'sass'...

[17:44:15] Finished 'sass' after 445 ms

[17:44:15] Starting 'images'...

[17:44:17] gulp-imagemin: Minified 1 image (saved 7.53 kB - 33.4%)

[17:44:17] Finished 'images' after 1.75 s

[17:44:17] Starting 'inline'...

[17:44:18] Finished 'inline' after 1.58 s

[17:44:18] Finished 'build' after 4.31 s

[17:44:18] Starting 'server'...

[17:44:18] Finished 'server' after 230 ms

[17:44:18] Starting 'watch'...

[BS] Access URLs:

 --------------------------------------

       Local: http://localhost:3002

    External: http://172.16.96.130:3002

 --------------------------------------

          UI: http://localhost:3003

 UI External: http://172.16.96.130:3003

 --------------------------------------

[BS] Serving files from: dist

 

And no more log lines after modifications.

 

Here's my environment:

  • Debian 8 jeessie
  • Foundation CLI version 2.1.0
  • node v0.12.13
  • npm v2.3.0

emails build gulp

When I modify the scss files, or the partials, or the layout, or the pages files,... I expect to see the changes automatically in the browser, but this is not what's happening. After starting the project and run the watch target, it does nothing when I modify the files.

[17:44:01] Requiring external module babel-register

[17:44:14] Using gulpfile /mnt/hgfs/koala/emails/KoalaEmails2/gulpfile.babel.js

[17:44:14] Starting 'default'...

[17:44:14] Starting 'build'...

[17:44:14] Starting 'clean'...

[17:44:14] Finished 'clean' after 13 ms

[17:44:14] Starting 'pages'...

[17:44:14] Finished 'pages' after 509 ms

[17:44:14] Starting 'sass'...

[17:44:15] Finished 'sass' after 445 ms

[17:44:15] Starting 'images'...

[17:44:17] gulp-imagemin: Minified 1 image (saved 7.53 kB - 33.4%)

[17:44:17] Finished 'images' after 1.75 s

[17:44:17] Starting 'inline'...

[17:44:18] Finished 'inline' after 1.58 s

[17:44:18] Finished 'build' after 4.31 s

[17:44:18] Starting 'server'...

[17:44:18] Finished 'server' after 230 ms

[17:44:18] Starting 'watch'...

[BS] Access URLs:

 --------------------------------------

       Local: http://localhost:3002

    External: http://172.16.96.130:3002

 --------------------------------------

          UI: http://localhost:3003

 UI External: http://172.16.96.130:3003

 --------------------------------------

[BS] Serving files from: dist

 

And no more log lines after modifications.

 

Here's my environment:

  • Debian 8 jeessie
  • Foundation CLI version 2.1.0
  • node v0.12.13
  • npm v2.3.0
Corey Schaaf over 3 years ago

Question: Are you able to open a browser and go to this URL:
http://localhost:3000/

If so, does it load your site? (this assumes your file is named index.html in the root of the dist folder). 

Also, remember that your styles are not inlined in the distribution folder when using the command

foundation watch

If you need your styles inlined (for production), you need to use the command

foundation build

Dani Castaños over 3 years ago

Hi Corey,

I see what's happening. I'm using a Virtual Machine where my Foundation Emails project is running, but the folder where it's executed is shared with my Mac, so I'm editting my files from the original source in my MAC and thus, the changes are not being detected. If I edit the files in my Debian VM, then the changes are detected...

Rafi Benkual over 3 years ago

I think this is a duplicate question to http://foundation.zurb.com/forum/posts/39825-browsersync-stops-working-after-two-reloads There was a PR merged today that addresses it. You can follow there to see the code change.