You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not a personal support request that should be posted on the Roots Discourse forums
Replace any X with your information.
What is the current behavior?
gulp watch crashes when doing minor CSS changes in a completely random fashion: a particular CSS change works one time (browser automatically refreshes, change shows up, gulp watch still running without error), then another time the exact same change makes gulp watch crash with the following error:
[03:53:21] Starting 'styles'...
assets\styles\main.scss
Error: File to import not found or unreadable: partials/home_page
Parent style sheet: D:/EasyPHP/www/pot/wp-content/themes/pot/assets/styles/main.scss
on line 4 of assets/styles/main.scss
>> @import "partials/home_page";
^
[03:53:21] Finished 'styles' after 7.96 ms
What is the expected or desired behavior?
Expected behavior: gulp watch shouldn't crash
Please describe your local environment:
WordPress version: 4.5.2
OS: Windows 10
NPM/Node version: 6.1.0
Where did the bug happen? Development or remote servers?
Local Apache server
The text was updated successfully, but these errors were encountered:
Submit a feature request or bug report
Replace any
X
with your information.What is the current behavior?
gulp watch
crashes when doing minor CSS changes in a completely random fashion: a particular CSS change works one time (browser automatically refreshes, change shows up, gulp watch still running without error), then another time the exact same change makesgulp watch
crash with the following error:What is the expected or desired behavior?
Expected behavior: gulp watch shouldn't crash
Please describe your local environment:
WordPress version: 4.5.2
OS: Windows 10
NPM/Node version: 6.1.0
Where did the bug happen? Development or remote servers?
Local Apache server
The text was updated successfully, but these errors were encountered: