Why isn't Hugo regenerating my SCSS files?

Featured image for sharing metadata for article

Over the last couple of days I've been - after a long hiatus - making some tweaks to my Hugo site's theme. I've hit an issue on both my laptop and (newly fresh installed Arch) PC, so it's worth writing it as a form of blogumentation.

I was finding that modifications to any SCSS files didn't trigger a rebuild of them πŸ€”

One thing very weird, is that even with my local setup modified to point to my local theme:

diff --git config.toml config.toml
index 39fef45f41..003150d38b 100644
--- config.toml
+++ config.toml
@@ -1,5 +1,7 @@
 baseURL = ""

+ignoreFiles = ['content/mf2']
+
 title = "Jamie Tanna | Software Engineer"

 languageCode = "en-GB"
@@ -287,4 +289,4 @@ slug = 2024
   path = '/week-notes/2024/**'

 [[module.imports]]
-path = "gitlab.com/jamietanna/www.jvt.me-theme"
+path = "./www.jvt.me-theme"

But when making changes to my local theme's SCSS, Hugo detected that there were changes, but didn't regenerate the styling.

It turns out it's because I was using Hugo, not Hugo (Extended), which adds the SCSS support.

As soon as I started using the Extended release, my builds now started allowing me to modify SCSS.

Written by Jamie Tanna's profile image Jamie Tanna on , and last updated on .

Content for this article is shared under the terms of the Creative Commons Attribution Non Commercial Share Alike 4.0 International, and code is shared under the Apache License 2.0.

#blogumentation #hugo.

This post was filed under articles.

Interactions with this post

Interactions with this post

Below you can find the interactions that this page has had using WebMention.

Have you written a response to this post? Let me know the URL:

Do you not have a website set up with WebMention capabilities? You can use Comment Parade.