search

michaelwayman / node-sass-chokidar

A thin wrapper around node-sass to replicate the --watch using chokidar instead of Gaze
MIT License
291 stars 34 forks source link

Upgrading from 1.2.2 to 1.3.3 stops generating new .css from .scss while app is runnig #67

Open iludart opened 6 years ago

iludart commented 6 years ago

When I manually stop the app and then use npm start to run it again all files are successfully created.

I'm running create-react-app using script: "start": "sh -ac '. ./.env; npm-run-all --parallel watch-css start-js"

which in turn executes in parallel: "watch-css": "node-sass-chokidar ./src/ --output ./src/ --watch" "start-js": "react-scripts start"

abisar commented 6 years ago

Same here. I upgraded to 1.3.* and now it seems like changes to my scss doesn't trigger watch or build.

    "build-css": "node-sass-chokidar src/ -o src/",
    "watch-css": "npm run build-css && node-sass-chokidar src/ -o src/ --watch",

I have only a single scss. Downgraded back to 1.1.0 and now it works again. If there is no major benefit in 1.3.* I'd rather stay in 1.1.0.

I followed create-react-app guide.

iludart commented 6 years ago

Well npm audit lists older versions as having vulnerabilities so it would be great to have a fix for this.

amz-x commented 6 years ago

Can confirm bug in v1.3.3, works in v1.3.0.

peterzebird commented 6 years ago

Same issue here, watch not working at all with v1.3.3 but works fine with v1.3.0

kapolos commented 5 years ago

Adding the --use-polling flag solved it for me.