# Full Hugo Pipes support (including SCSS/SASS) finally on Netlify

**URL:** <https://discourse.gohugo.io/t/full-hugo-pipes-support-including-scss-sass-finally-on-netlify/17581>\
**Category:** Announcements\
**Created:** [March 14, 2019, 8:02pm UTC](https://discourse.gohugo.io/t/full-hugo-pipes-support-including-scss-sass-finally-on-netlify/17581 "2019-03-14T20:02:07Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![bep](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/bep/32/3332_2.png) [@bep](https://discourse.gohugo.io/u/bep)\
**Post date:** [March 14, 2019, 8:02pm UTC](https://discourse.gohugo.io/t/full-hugo-pipes-support-including-scss-sass-finally-on-netlify/17581/1 "2019-03-14T20:02:07Z")

</div>

> **[A more flexible build architecture with updated Linux | Netlify](https://www.netlify.com/blog/2019/03/14/a-more-flexible-build-architecture-with-updated-linux/?utm_source=twitter&utm_medium=social&utm_campaign=blog)**
>
> One of our primary goals at Netlify is to make deployments something you don’t have to worry about. With that in mind, we designed our process for making a site from Git so that it “just works” with very little configuration. We get daily feedback...

---

<div class="post-metadata">

**Author:** ![bep](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/bep/32/3332_2.png) [@bep](https://discourse.gohugo.io/u/bep)\
**Post date:** [March 14, 2019, 8:04pm UTC](https://discourse.gohugo.io/t/full-hugo-pipes-support-including-scss-sass-finally-on-netlify/17581/2 "2019-03-14T20:04:20Z")

</div>

Pinned globally on March 14, 2019, 8:04pm UTC



---

<div class="post-metadata">

**Author:** ![zwbetz](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/zwbetz/32/16088_2.png) [@zwbetz](https://discourse.gohugo.io/u/zwbetz)\
**Post date:** [March 14, 2019, 8:09pm UTC](https://discourse.gohugo.io/t/full-hugo-pipes-support-including-scss-sass-finally-on-netlify/17581/3 "2019-03-14T20:09:57Z")

</div>

Exciting news. And now the theme maintainers will have one less thing to worry about (all the checklist items for themes that use Hugo Pipes) 🙂

---

<div class="post-metadata">

**Author:** ![alexandros](https://avatars.discourse-cdn.com/v4/letter/a/ecc23a/32.png) [@alexandros](https://discourse.gohugo.io/u/alexandros)\
**Post date:** [March 14, 2019, 9:38pm UTC](https://discourse.gohugo.io/t/full-hugo-pipes-support-including-scss-sass-finally-on-netlify/17581/4 "2019-03-14T21:38:18Z")

</div>

> [@zwbetz](#):
>
> And now the theme maintainers will have one less thing to worry about (all the checklist items for themes that use Hugo Pipes)

Not really. A theme _needs_ to work with the Basic version of Hugo in my not so humble opinion.

There are those of us who do not rely on SCSS/PostCSS in their workflows.

---

<div class="post-metadata">

**Author:** ![zwbetz](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/zwbetz/32/16088_2.png) [@zwbetz](https://discourse.gohugo.io/u/zwbetz)\
**Post date:** [March 15, 2019, 12:09am UTC](https://discourse.gohugo.io/t/full-hugo-pipes-support-including-scss-sass-finally-on-netlify/17581/5 "2019-03-15T00:09:31Z")

</div>

Ah, good point

---

<div class="post-metadata">

**Author:** ![FelicianoTech](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/felicianotech/32/22886_2.png) [@FelicianoTech](https://discourse.gohugo.io/u/FelicianoTech)\
**Post date:** [March 15, 2019, 1:30am UTC](https://discourse.gohugo.io/t/full-hugo-pipes-support-including-scss-sass-finally-on-netlify/17581/6 "2019-03-15T01:30:45Z")

</div>

> [@alexandros](#):
>
> Not really. A theme _needs_ to work with the Basic version of Hugo in my not so humble opinion.

What’s the difference? The Hugo build process is exactly the same.

---

<div class="post-metadata">

**Author:** ![zwbetz](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/zwbetz/32/16088_2.png) [@zwbetz](https://discourse.gohugo.io/u/zwbetz)\
**Post date:** [March 15, 2019, 1:38am UTC](https://discourse.gohugo.io/t/full-hugo-pipes-support-including-scss-sass-finally-on-netlify/17581/7 "2019-03-15T01:38:53Z")

</div>

I can think of one now that @alexandros brought this up.  
Say I’m on Windows 32 bit (which doesn’t have extended version available) and I want to use a theme that was made with Hugo Pipes. I’d be out of luck to run/test my site locally.

---

<div class="post-metadata">

**Author:** ![FelicianoTech](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/felicianotech/32/22886_2.png) [@FelicianoTech](https://discourse.gohugo.io/u/FelicianoTech)\
**Post date:** [March 15, 2019, 1:45am UTC](https://discourse.gohugo.io/t/full-hugo-pipes-support-including-scss-sass-finally-on-netlify/17581/8 "2019-03-15T01:45:51Z")

</div>

Ah okay. I didn’t think the extended version wouldn’t be available on a platform such as Windows. I don’t believe there should be a regular and extended release at all. Extended should be built statically and available everywhere.

I wonder why Windows 32bit doesn’t have extended but I guess that’s a different discussion.

Thanks for providing more info.

---

<div class="post-metadata">

**Author:** ![alexandros](https://avatars.discourse-cdn.com/v4/letter/a/ecc23a/32.png) [@alexandros](https://discourse.gohugo.io/u/alexandros)\
**Post date:** [March 15, 2019, 8:58am UTC](https://discourse.gohugo.io/t/full-hugo-pipes-support-including-scss-sass-finally-on-netlify/17581/9 "2019-03-15T08:58:19Z")

</div>

> [@FelicianoTech](#):
>
> Extended should be built statically and available everywhere.

There are various issues with the above that’s why it was not implemented. See the following:

> <https://github.com/gohugoio/hugo/issues/4985>
>
> It's obviously a huge win to have statically linked binaries, since they are max…imally portable.
> 
> The new extended binaries with integrated SASS support are being built as dynamically linked executables. These don't work in my minimal container, since I don't have the required dynamic libraries.  
> 
> Was this by design, or is it something you can easily fix?
> 
> (The integrated SASS support is great BTW.)

> <https://github.com/gohugoio/hugo/issues/5166>
>
> Hello,
> 
> it is not possible to use the hugo binary file in the current release …on CentOS due to missing support.
> 
> strings /usr/lib64/libstdc++.so.6 | grep GLIBCXX
> ....
> GLIBCXX\_3.4.19
> 
> Hugo seems to be needing GLIBCXX \>= 3.4.20

> <https://github.com/gohugoio/hugo/issues/5148>
>
> This Netlify issue is taking its time:
> 
> https://github.com/netlify/build-image…/issues/183
> 
> I was reminded of this issue watching this talk:
> 
> https://www.youtube.com/watch?v=hWNwI5q01gI
> 
> They are not building a static binary because of some parts of the \`glibc\` that requires dynamic linking. 
> 
> We build fully static binaries for Windows, because the common Windows user does not hav \`glibc\` installed. On Linux and macOS this is common.
> 
> On minimal Docker setups (as Netlify) is, this is more common.
> 
> I see no technical issues building fully static binaries. That should just work.
> 
> My concerns have been:
> 
> \* Bigger binaries. I suspect it would go from 10 to 50 mb.
> \* I have also seen security been used as an argument. As a bug in \`glibc\` could be patched faster when dynamically linked.
> 
> I'll leave this open-ended.

---

<div class="post-metadata">

**Author:** ![FelicianoTech](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/felicianotech/32/22886_2.png) [@FelicianoTech](https://discourse.gohugo.io/u/FelicianoTech)\
**Post date:** [March 15, 2019, 12:39pm UTC](https://discourse.gohugo.io/t/full-hugo-pipes-support-including-scss-sass-finally-on-netlify/17581/10 "2019-03-15T12:39:28Z")

</div>

All three of those Issues show why static would be better than dynamic.

The only two real issues I’ve seen are:

1. Larger binaries - this is a minor issue. I would think most people won’t complain/be prohibited from using Hugo.
2. Possible security vulnerabilities - This is a fair thought but the larger attack vector is in the number of modules Hugo already pulls in on the Go side. Aside from this past month, Hugo is updated fairly frequently, more so than almost any other tool I use, so personally I’m not worried about the delay in time to deliver a fix.

* * *

I assume Hugo extended needs libc in the first place because of SASS support right? And if one day there’s a SASS library written in pure Go, then maybe we can avoid this issue entirely?

---

<div class="post-metadata">

**Author:** ![bep](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/bep/32/3332_2.png) [@bep](https://discourse.gohugo.io/u/bep)\
**Post date:** [March 15, 2019, 1:57pm UTC](https://discourse.gohugo.io/t/full-hugo-pipes-support-including-scss-sass-finally-on-netlify/17581/11 "2019-03-15T13:57:30Z")

</div>

> [@FelicianoTech](#):
>
> Extended should be built statically and available everywhere.

The extended version requires a C++ build chain for the target platform (unless you want to implement SASS support in native Go). I spent 2 long working days to get a build setup for 3 OSes (Windows 64 bit, macOS and Linux). And that is the OSes I can easily test on.

This thread reminds me of of this tweet:

[https://twitter.com/Madisonkanna/status/1106348372040937472](https://twitter.com/Madisonkanna/status/1106348372040937472)

---

<div class="post-metadata">

**Author:** ![FelicianoTech](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/felicianotech/32/22886_2.png) [@FelicianoTech](https://discourse.gohugo.io/u/FelicianoTech)\
**Post date:** [March 15, 2019, 2:05pm UTC](https://discourse.gohugo.io/t/full-hugo-pipes-support-including-scss-sass-finally-on-netlify/17581/12 "2019-03-15T14:05:13Z")

</div>

> [@bep](#):
>
> This thread reminds me of of this tweet:

It shouldn’t.

No one is shouting, at least I’m not. We’re having a discussion on dynamic/static libs and how themes requiring SASS support could hinder some users. We all really appreciate the work you do @bep.

---

<div class="post-metadata">

**Author:** ![Jura](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/jura/32/13581_2.png) [@Jura](https://discourse.gohugo.io/u/Jura)\
**Post date:** [March 15, 2019, 2:32pm UTC](https://discourse.gohugo.io/t/full-hugo-pipes-support-including-scss-sass-finally-on-netlify/17581/13 "2019-03-15T14:32:09Z")

</div>

Good news! Thanks to Netlify for making this, makes working with Hugo a bit easier on their platform.

Seems to work fine for me too, although total deploy time is a bit slower (1:54 versus 1:06) but everything else is the same. 🙂

---

<div class="post-metadata">

**Author:** ![zwbetz](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/zwbetz/32/16088_2.png) [@zwbetz](https://discourse.gohugo.io/u/zwbetz)\
**Post date:** [March 15, 2019, 2:46pm UTC](https://discourse.gohugo.io/t/full-hugo-pipes-support-including-scss-sass-finally-on-netlify/17581/14 "2019-03-15T14:46:44Z")

</div>

Nice @Jura.

My apologies for taking this thread off topic. Do let it be known I’m thankful to Netlify team and Bep (and the many contributors) for all their hard work. 💪