Skip to content

Conversation

@ThorntonStuart
Copy link

Probably doesn't even warrant a pull request, but never done one before and fixes a bug that I was having! Otherwise really enjoyed the blog and everything is working great.

@donovanmuller
Copy link
Contributor

Great to hear you're enjoying the blog and thanks for the PR!

Could you elaborate more on the errors you were getting?
browsersync was not a typo as it references the Gulp task called browsersync and not the browser-sync plugin.

If I run this locally as is, it works (it always does though 😄).
Could you please provide the error you were getting as well as your environment?

I also just added an update regarding the Node version to use, if by some chance it could be related to that. See here

@ThorntonStuart
Copy link
Author

Hmm strange. I did figure that it might not be a mistake when I found it again in the watch-js file. The issue I got prior to the first commit was:

Unhandled rejection Error: Task browsersync is not configured as a task on gulp. If this is a submodule, you may need to use require('run-sequence').use(gulp).

Adding the dash fixed this error, and 'gulp ghost' would run, but then saving the .hbs would trigger the error from the watch.js file:

Task 'browsersync:reload' is not in your gulpfile

And strangely adding the dash fixed this too. Thought it might be a 'run-sequence' issue but then obviously the dashes fixed it so didn't explore that possibility after that.

@donovanmuller
Copy link
Contributor

Weird indeed. What platform you running on?

@ThorntonStuart
Copy link
Author

Running El Capitan 10.11.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants