I’ve been having issues with trying to set up Bedrock and Sage and had a lot of trial and error to at least get this setup (with SASS) to work on my VM local. I’m currently stuck on compiling SCSS to process variables. I’ve looked at a few topics including one created 10 days ago where the solutions do not work for me.
I’ve updated Sage, Bud, and all necessary extensions to 6.12, added PurgeCSS, and configured my bud.config.js file. It’s still giving me compiled CSS like the following:
I’m not certain what to do at this point. I’ve set up Sage 9 in the past which worked for me, but Sage 10 seems to give me more troubles. Any help on why this isn’t working for me would be appreicated. I also set up a repo for someone to take a look at my files if I’m missing anything.
A modified Sage 10 example theme with SCSS support:
Clone that repository and invoke nvm use; npm install; npm run build.
The output app.[...].css and editor.[...].css (in public/css/) directory should both contain the correctly parsed and processed SCSS as valid CSS.
Steps that were taken for preparing this repository (that is known to work correctly with SCSS) (you can also just follow the commits of that repository):
Create the theme using composer (from latest master commit): $ composer create-project roots/sage sage10-scss
I had to use the latest master commit (dev-master) as otherwise the @roots/bud-postcss own dependencies would be incompatible with the Sage theme dependencies.
Feel free to provide all of the exact steps for a minimal reproduction of this issue if you’d like to see this topic listed again. It’s not fair to ask folks to dig through a repo… especially when your screenshots provided here don’t even match what’s in your repo.
Ok, I did yet another reinstallation of my theme following the exact steps, including adding all of the linting extensions, and it looks like I’m no longer running into this issue.
I also used @strarsistip of making sure to add the tilde sign before the source url in the @font-face declaration, and that is at least resolving and pointing to the correct file. I’m still having an issue of my fonts not actually displaying, but that is another topic I may or may not create.