Skip to content
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

Open
AndreaBarghigiani opened this issue Nov 18, 2019 · 7 comments
Open

Not watching SCSS changes on new installations #176

AndreaBarghigiani opened this issue Nov 18, 2019 · 7 comments

Comments

@AndreaBarghigiani
Copy link

AndreaBarghigiani commented Nov 18, 2019

Bug Report

I have installed WPGulp with npx wpgulp on a fresh theme and start using it with npm start after I've edited the wpgulp.config.js file but when I save some changes on my SCSS files Gulp does not compile them in a new style.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 the styles task when I edit my SCSS files.

Steps to Reproduce

  1. install with npx wpgulp
  2. (optional) edit configuration in wpgulp.config.js
  3. run npm start

Packages versions

  1. node -v: v10.16.0
  2. npm -v: 6.9.0

Then, specify:

  1. Operating system: MacOS Mojave 10.14.6

Possible Solution
The strange thing is that if I take package.json, gulpfile.babel.js and wpgulp.config.js from an older project where everything works just fine and I run npm install, after the installation is completed, when I run npm 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.

@wazynski
Copy link

wazynski commented Mar 2, 2020

Having the exact same issue:

node -v: v11.15.0
npm -v: 6.10.3
Operating system: MacOS Mojave 10.14.6

@CatinhoCR
Copy link

Is this still a thing?

@chstappert
Copy link

It's still an issue:
BigSur 11.1
npm -v 6.14
node -v 14.15.4

@chstappert
Copy link

It's still an issue:
BigSur 11.1
npm -v 6.14
node -v 14.15.4

Got it running. The "const watchStyles" wasn't correctly set. Now it works perfectly! Great tool.

@jvanstone
Copy link

It's still an issue:
BigSur 11.1
npm -v 6.14
node -v 14.15.4

Got it running. The "const watchStyles" wasn't correctly set. Now it works perfectly! Great tool.

What did you change it too??

@Web-Assembler
Copy link

@jvanstone The fix mentioned by @chstappert worked for me. The watchStyles was set to const watchStyles = './assets/css/**/*.scss'; whereas I'm putting all my scss files inside assets/scss so I simply changed it to const watchStyles = './assets/scss/**/*.scss'; Thanks!

@jvanstone
Copy link

@jvanstone The fix mentioned by @chstappert worked for me. The watchStyles was set to const watchStyles = './assets/css/**/*.scss'; whereas I'm putting all my scss files inside assets/scss so I simply changed it to const watchStyles = './assets/scss/**/*.scss'; Thanks!

@Web-Assembler thanks the response. I was able to get it to work too. Thanks!

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

No branches or pull requests

6 participants