# Gulp stuck on “Starting 'hbsWatcher'” when running Ghost Casper theme locally

**URL:** <https://forum.ghost.org/t/gulp-stuck-on-starting-hbswatcher-when-running-ghost-casper-theme-locally/13800>\
**Category:** Developer help\
**Created:** [April 24, 2020, 5:33am UTC](https://forum.ghost.org/t/gulp-stuck-on-starting-hbswatcher-when-running-ghost-casper-theme-locally/13800 "2020-04-24T05:33:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![markjackson02](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/markjackson02/32/6028_2.png) [@markjackson02](https://forum.ghost.org/u/markjackson02)\
**Post date:** [April 24, 2020, 5:33am UTC](https://forum.ghost.org/t/gulp-stuck-on-starting-hbswatcher-when-running-ghost-casper-theme-locally/13800/1 "2020-04-24T05:33:46Z")

</div>

I am trying to run the [Casper theme](https://github.com/TryGhost/Casper) locally. Per the docs I ran `yarn install` successfully but when I run `yarn dev` it gets stuck. Here are the logs:

```auto
$ yarn run dev
yarn run v1.22.4
warning casper@3.0.6: The engine "ghost" appears to be invalid.
warning casper@3.0.6: The engine "ghost-api" appears to be invalid.
$ gulp
[01:03:02] Using gulpfile ~\Documents\workspace\casper-hps\gulpfile.js
[01:03:02] Starting 'default'...
[01:03:02] Starting 'css'...
[01:03:06] Finished 'css' after 4.38 s
[01:03:06] Starting 'js'...
[01:03:07] Finished 'js' after 692 ms
[01:03:07] Starting 'serve'...
[01:03:07] Finished 'serve' after 9.81 ms
[01:03:07] Starting 'cssWatcher'...
[01:03:07] Starting 'hbsWatcher'...

```

It gets stuck on `Starting 'hbsWatcher'`.

I am getting the same result on both my Windows 7 and Windows 10 PCs.

Any ideas what could be causing this?

Note: I made a [post on StackOverflow](https://stackoverflow.com/questions/61401645/gulp-stuck-on-starting-hbswatcher-when-running-ghost-casper-theme-locally) with this question before I found this forum. I’ll make sure to update both if a solution arises.

---

<div class="post-metadata">

**Author:** ![minimaluminium](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/minimaluminium/32/2652_2.png) [@minimaluminium](https://forum.ghost.org/u/minimaluminium)\
**Post date:** [April 24, 2020, 5:53am UTC](https://forum.ghost.org/t/gulp-stuck-on-starting-hbswatcher-when-running-ghost-casper-theme-locally/13800/2 "2020-04-24T05:53:39Z")

</div>

I assume it’s not stuck. Instead Gulp just started 2 watchers (`cssWatcher` and `hbsWatcher`) and waiting for files to be updated. When you update .css or .hbs file, those watchers will work respectively and do tasks such as auto-prefixing, live-reloading etc.

---

<div class="post-metadata">

**Author:** ![markjackson02](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/markjackson02/32/6028_2.png) [@markjackson02](https://forum.ghost.org/u/markjackson02)\
**Post date:** [April 24, 2020, 6:50am UTC](https://forum.ghost.org/t/gulp-stuck-on-starting-hbswatcher-when-running-ghost-casper-theme-locally/13800/3 "2020-04-24T06:50:05Z")

</div>

Ok yes that is correct. I was expecting a success message. When I change the .hbs file the console shows it being compiled. Thanks!

---

<div class="post-metadata">

**Author:** ![tkeriduN](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/tkeridun/32/13147_2.png) [@tkeriduN](https://forum.ghost.org/u/tkeriduN)\
**Post date:** [May 11, 2021, 12:26am UTC](https://forum.ghost.org/t/gulp-stuck-on-starting-hbswatcher-when-running-ghost-casper-theme-locally/13800/4 "2021-05-11T00:26:15Z")

</div>

Having the same issue, except my files aren’t getting compiled.

_Edit_

And now I found why. I was using node version 16.1.0 while ghost only supports version up to 14.15.0.

Told nvm to use v14.15.0 and restarted ghost, then ran “yarn dev” again, now it’s compiling as it should.

_Edit_

Nope. Apparently it only compiles once, at starting of yarn dev. The “css” task runs but  
watcher seems to be lost. I’ll take a look at the gulpfile and see if I’ve got something misconfigured. However I can’t remember changing anything there.