Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hugo Pipes uses LibSass, but it is not fully compatible with the latest Sass specification and does lack features like the new module system. I used Hugo Pipes to convert SCSS to CSS and to add Subresource Integrity (SRI).
Dart Sass is now used to process the .scss files. It runs in the build pipeline after Hugo. Hugo moves all files and folders in the static directory to the output directory. Dart Sass processes the content of the [outputDir]/style directory and removes all .scss files afterwards.
Currently, all .scss files are processed, but this does only take up a few more bytes on the server — the browser will only download the .css files it needs.
I removed SRI. Honestly, I only used it because it was so easy to add. Because I'm currently not using a CDN and SRI can sometimes lead to problems (it was with caching, if I remember correctly), I will not add it again in the near future.