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

[BUG] style.css.liquid in assets breaks watcher #144

Closed
marioloncarek opened this issue Oct 20, 2021 · 1 comment
Closed

[BUG] style.css.liquid in assets breaks watcher #144

marioloncarek opened this issue Oct 20, 2021 · 1 comment
Labels
bug Something isn't working released

Comments

@marioloncarek
Copy link

Describe the bug
When you put .css.liquid file in the assets it breaks the watcher (packer start) and it will not update css or js. Deploy does not have that issues.

To Reproduce
Steps to reproduce the behavior:

  1. put file.css.liquid in assets
  2. packer start
  3. terminal shows this error:

custom.css.liquid: no such file or directory

Expected behavior
watcher working after adding .css.liquid files to assets

System (please complete the following information):

  • OS: OSX
  • Node Version: v14 LTS
  • NPM Version: latest

Packer (please complete the following information):

  • Version: 2.2.0

Theme (please complete the following information):

  • custom based od Dawn from shopify
@marioloncarek marioloncarek added the bug Something isn't working label Oct 20, 2021
danielbeardsley added a commit to iFixit/shopify-packer that referenced this issue Mar 1, 2022
somefile.css.liquid was being picked up as a "liquid" file and we
assumed it definitely *wasn't* in the dist/assets dir. This is sometimes
not true (we can have liquid files in the assets dir).

Since the paths we get are already relative to the assets dir, let's
just use path joining and normalization to handle those cases. All this
function can do is exclude some files, it can't move them. So we
shouldn't be trying to *create* new paths based on extensions.

Fixes hayes0724#144
hayes0724 pushed a commit that referenced this issue Mar 9, 2022
somefile.css.liquid was being picked up as a "liquid" file and we
assumed it definitely *wasn't* in the dist/assets dir. This is sometimes
not true (we can have liquid files in the assets dir).

Since the paths we get are already relative to the assets dir, let's
just use path joining and normalization to handle those cases. All this
function can do is exclude some files, it can't move them. So we
shouldn't be trying to *create* new paths based on extensions.

Fixes #144
github-actions bot pushed a commit that referenced this issue Mar 9, 2022
## [2.4.4](v2.4.3...v2.4.4) (2022-03-09)

### Bug Fixes

* Build exit non zero on failure ([#153](#153)) ([8b595f9](8b595f9))
* Environment vars: allow them to work ([#184](#184)) ([009f704](009f704))
* handle {file}.css.liquid assets correctly ([0f8e0ce](0f8e0ce)), closes [#144](#144)
* ssl:make timing bug ([#180](#180)) ([bec0e9e](bec0e9e))
@github-actions
Copy link
Contributor

github-actions bot commented Mar 9, 2022

🎉 This issue has been resolved in version 2.4.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

Dejanimitrijevic pushed a commit to Dejanimitrijevic/shopify-packer that referenced this issue May 28, 2024
## [2.4.4](hayes0724/shopify-packer@v2.4.3...v2.4.4) (2022-03-09)

### Bug Fixes

* Build exit non zero on failure ([#153](hayes0724/shopify-packer#153)) ([8b595f9](hayes0724/shopify-packer@8b595f9))
* Environment vars: allow them to work ([#184](hayes0724/shopify-packer#184)) ([009f704](hayes0724/shopify-packer@009f704))
* handle {file}.css.liquid assets correctly ([0f8e0ce](hayes0724/shopify-packer@0f8e0ce)), closes [#144](hayes0724/shopify-packer#144)
* ssl:make timing bug ([#180](hayes0724/shopify-packer#180)) ([bec0e9e](hayes0724/shopify-packer@bec0e9e))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working released
Projects
None yet
Development

No branches or pull requests

1 participant