Support extended Hugo version

[DirtyF]

Duplicate of: netlify/binrc#16
Opening an issue here as @futuregerald kindly suggested.

- What is the current behavior?

From version 0.43 Hugo comes in two flavours, extended version allows native Sass compilation.
Netlify currently does not support extended version:

2:28:30 PM: ERROR 2018/07/10 12:28:30 error: failed to transform resource: failed to transform “scss/main.scss” (text/x-scss): this feature is not available in your current Hugo version

Edit: For now, the recommended workflow is to commit your /resources folder after building locally with hugo.

- What is the expected behavior?

Either download the extended binary by default from now on or allow to specify something like 0.43/extended in netlify.toml.

_extended is added to the release path before the version number:

https://github.com/gohugoio/hugo/releases/download/v0.43/hugo_0.43_Linux-64bit.tar.gz
https://github.com/gohugoio/hugo/releases/download/v0.43/hugo_extended_0.43_Linux-64bit.tar.gz

[nolessafool]

the issue on binrc is the one to watch for a resolution.

In the meantime, 1 potential workaround which is not ideal:

follow bep's advice:
https://twitter.com/GoHugoIO/status/1016706519507881986

[jensamunch]

i tried manually including binary in the repo - as a quick-fix - doesn't work:

6:20:18 PM: Executing user command: ./hugo --config paceup.com.toml,config.toml
6:20:18 PM: ./hugo: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by ./hugo)
6:20:18 PM: ./hugo: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by ./hugo)

[nolessafool]

We'll track that separate issue here, @jensamunch : #183

[baublet]

To those looking for a workaround until this is fixed:

Run hugo locally with the extended version, then check in your resources/_gen/assets directory to the repository so that Hugo skips trying to generate the assets.

[jensamunch]

It would be really great to have a bit more of an explanation from the Netlify team on timeline and plan.

[brycekahle]

@jensamunch Unfortunately, the solution involves upgrading the version of Ubuntu we use in the base image. That is a larger user impact than we initial hoped for. In order to ensure a smooth transition for all users, we need to do some work around communicating the changes ahead of time. Once we have a firm timeline, we will communicate that publicly.

[igk1972]

Fast workaround #183 (comment)