I’m using Hugo’s built-in SCSS compilation feature, with a single entry point named main.scss. Here’s how I call the file: {{ $options := (dict "targetPath" "/css/main.min.css" "outputStyle" "compressed" "enableSourceMap" true) }} {{ $style := resources.Get "scss/main.scss" | resources.ToCSS $opti…

You can copy it to your assets folder and rename it to scss. That definitely works. My workflow: I don’t use the node_modules files directly but copy them via npm script to my assets folder. From there I import them, rename and change them if necessary and compare them later to the originals in cas…

Thanks for the suggestion Leo! I wish I could reference the node_modules files directly, but this will do the trick for now. :slight_smile:

[image] fbnlsr: I wish I could reference the node_modules files directly Basically you can but in case of SCSS it’s different. But don’t underestimate the advantage of doing up front a bit more work for copying but afterwards being able to edit the (former) node_modules files and automaticall…

[SOLVED] Hugo fails to import regular .css file @import in .scss

support

Marcel_Overdijk June 1, 2020, 11:35am 5

See here Including css file from node_modules in scss

Topic		Replies	Views
ToCss failing when importing regular .css file support	4	1422	November 29, 2018
Include scss via hugo module support	10	4956	November 13, 2020
Including css file from node_modules in scss	6	20350	June 1, 2020
Moving to Hugo modules with a theme using SCSS support modules , postprocess	5	2440	February 21, 2022
Working example of Hugo Modules and Bootstrap .scss files? support	9	4259	May 6, 2020

[SOLVED] Hugo fails to import regular .css file @import in .scss

Related topics