Theme will not compile when using the Hugo 'lite' binary which does not include Hugo Pipes about hugo-hero-theme HOT 3 CLOSED

I just tested the theme and was able to change the .scss files and see them update live while running hugo server. This theme does uses Hugo pipelines and it is implemented correctly.

Given that you are running hugo server from the hugo site root, and you see the server running in the terminal. Any change to a .scss file in the /themes/hugo-hero-theme/assets/scss/ folder should live refresh in the browser. You should also see that file change in the terminal as Hugo updates the file.

If you are not seeing the changes. Then maybe try disabling your cache in chrome devtools. In the network tab there is a disable cache tickbox. Sometimes it is also helpful to delete the public directory from the root of the project and run hugo again. Sometimes this clears out old files.

from hugo-hero-theme.

Thanks for the reply. I'm adding some notes here in case anyone else runs into same.

Hugo did not complain until I removed the _gen directory. Then, I got an (almost) useful error, "failed to transform resouce: TOCSS: failed to transform "scss/style.scss" (text/x-scss): this feature is not available in your current Hugo version:

Searches reveal I need to build the "extended" version of Hugo. In the Hugo source dir:

go get -d github.com/wellington/go-libsall/libs
go install --tags extended

After that hugo version should report version with "/extended" appended. Now restart hugo server to see scss changes.

from hugo-hero-theme.

You absolutely right. There are now 2 binaries of Hugo floating about. And it's really not clear which version you have installed. I'm on a mac and I used brew to install Hugo, and I guess it just comes as the extended version. But yeah if you get it another way or your on Windows you might end up with the 'lite' version.

I also had this issue when deploying to Netlify. Apparently they (or they did, they may have fixed it) use the lite version, so if you don't upload the _resources folder (which is their workaround) then you will get a similar error about having the wrong hugo version. Of course it's nothing to do with the version requirement, it's that Netlify is not using the extended version for the build.

from hugo-hero-theme.