Shopify/slate

slate-tools start generating style-tags.liquid without including theme.scss.

sarhov opened this issue · 5 comments

sarhov commented

Problem

When I slate-tools build, it generate correct style-tags.liquid.

{%- if layout == 'theme' -%}
<link type="text/css" href="{{ 'layout.theme.css' | asset_url }}" rel="stylesheet">
{%- else -%}
<link rel="prefetch" href="{{ 'layout.theme.css' | asset_url }}" as="style">
{%- endif -%} {%- if layout == 'theme' -%}
<link type="text/css" href="{{ 'layout.theme.styleLiquid.scss.css' | asset_url }}" rel="stylesheet">
{%- else -%}
<link rel="prefetch" href="{{ 'layout.theme.styleLiquid.scss.css' | asset_url }}" as="style">
{%- endif -%} {%- if template == 'product' -%}
<link type="text/css" href="{{ 'template.product.css' | asset_url }}" rel="stylesheet">
{%- else -%}
<link rel="prefetch" href="{{ 'template.product.css' | asset_url }}" as="style">
{%- endif -%}

But slate-tools start command generating style-tags.liquid where only styleLiquid scss is included


  
  
  
  
    
  
  
    {%- if layout == 'theme' -%}
      <link type="text/css" href="{{ 'layout.theme.styleLiquid.scss.css' | asset_url }}" rel="stylesheet">
    {%- else -%}
      <link rel="prefetch" href="{{ 'layout.theme.styleLiquid.scss.css' | asset_url }}" as="style">
    {%- endif -%}

More Information

OS: WIndows 10
Node: v10.15.3
npm: 6.9.0

The same issue with yarn build.

curiouscrusher commented

@sarhov I just ran into this issue today also. I'll follow up if I find out what's going on with the different results.

LucaDe commented

Same issue here. Did you find any workarounds?

curiouscrusher commented

@LucaDe After looking at the generated code deeper it turns out that both the outputs are correct, the slate-tools build command simply generates the extra prefetch links that are useful in production, as well as including the additional product styles chunk.

I ran into this when I was debugging an IE 11 error that I thought was related to missing code, turns out it was actually just in need of a polyfill 🤷‍♂ So to me it doesn't seem like there's actually an issue here, just an expected difference in the production code vs dev/HMR code.

sarhov commented

@sarhov I just ran into this issue today also. I'll follow up if I find out what's going on with the different results.

@curiouscrusher

No solution yet, I am continuing use ThemeKit instead.

curiouscrusher commented

@sarhov what's the problem you're having here? Are you running into missing compiled assets, or just looking to find out what the differences in asset url's are for?