-
-
Notifications
You must be signed in to change notification settings - Fork 303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not watching SCSS changes on new installations #176
Comments
Having the exact same issue: node -v: v11.15.0 |
Is this still a thing? |
It's still an issue: |
Got it running. The "const watchStyles" wasn't correctly set. Now it works perfectly! Great tool. |
What did you change it too?? |
@jvanstone The fix mentioned by @chstappert worked for me. The watchStyles was set to |
@Web-Assembler thanks the response. I was able to get it to work too. Thanks! |
Bug Report
I have installed WPGulp with
npx wpgulp
on a fresh theme and start using it withnpm start
after I've edited thewpgulp.config.js
file but when I save some changes on my SCSS files Gulp does not compile them in a newstyle.css
file.Expected Behavior
Watching any changes in my SCSS files.
Actual Behavior
WPGulp runs once when I type
npm start
and does not run thestyles
task when I edit my SCSS files.Steps to Reproduce
npx wpgulp
wpgulp.config.js
npm start
Packages versions
node -v
: v10.16.0npm -v
: 6.9.0Then, specify:
Possible Solution
The strange thing is that if I take
package.json
,gulpfile.babel.js
andwpgulp.config.js
from an older project where everything works just fine and I runnpm install
, after the installation is completed, when I runnpm start
everything works just fine.Those are the files that I import:
wpgulp-files.zip
I've also tried to run
npx install-wpgulp
on this working project to update my files with the latest version but the update make my WPGulp stop watching for file changes.I've also checked for differences between the downloaded files and the working ones but, except variable values and small syntax changes, I do not see any relevant.
The text was updated successfully, but these errors were encountered: