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
When running theme watch I get the following behaviour:
✅ a direct change to /assets/app.css successfully uploads /assets/app.css.
✅ a change to the build entry file /src/app.scss triggers a build and successfully uploads /assets/app.css.
❌ a change to /src/components/helloWorld.scssdoes trigger a build, updating /assets/app.css as expected, but /assets/app.cssis not uploaded.
If I make a change to /src/components/helloWorld.scss and then theme deploy assets/app.css it does successfully upload the change, as expected.
Update: To clarify I have gulp watch running in a second terminal window which watches the /src directory for changes, and triggers a /assets/app.css build when a change is received.
The text was updated successfully, but these errors were encountered:
This is an issue with Themekit v1.0.0, reverting to v0.8.1 fixes this issue. My guess is the issue was introduced in #601.
I run my build process with Gulp. It takes the entry file at
/src/app.scss
and generates/assets/app.css
, which is used in mytheme.liquid
template.Directory structure:
When running
theme watch
I get the following behaviour:/assets/app.css
successfully uploads/assets/app.css
./src/app.scss
triggers a build and successfully uploads/assets/app.css
./src/components/helloWorld.scss
does trigger a build, updating/assets/app.css
as expected, but/assets/app.css
is not uploaded.If I make a change to
/src/components/helloWorld.scss
and thentheme deploy assets/app.css
it does successfully upload the change, as expected.Update: To clarify I have
gulp watch
running in a second terminal window which watches the/src
directory for changes, and triggers a/assets/app.css
build when a change is received.The text was updated successfully, but these errors were encountered: