I recall downloading an earlier version of sage 10 and I was able to choose a css framework, like Tailwind or Bulma etc. I cloned down the latest sage 10 and that framework option seems to no longer be present, having followed the installation steps in the Github repo for that branch. The steps fro naming your theme also appear to be gone.
Thanks for the reply @Log1x! I appreciate it. I’m hoping to get further guidance here.
I’m getting closer. I’m currently stopped when running yarn start.
I get an error: ERROR Failed to compile with 2 errors
These dependencies were not found:
* -!../../../node_modules/css-loader/dist/cjs.js??ref--5-2!../../../node_modules/postcss-
loader/src/index.js??postcss0!./common/global in ./node_modules/css-loader/dist/cjs.js??ref--5-
2!./node_modules/postcss-loader/src??postcss0!./resources/assets/styles/app.css
* -!../../../node_modules/css-loader/dist/cjs.js??ref--5-2!../../../node_modules/postcss-
loader/src/index.js??postcss0!bootstrap/scss/bootstrap in ./node_modules/css-loader/dist/cjs.js??ref--5-
2!./node_modules/postcss-loader/src??postcss0!./resources/assets/styles/app.css
I’ve run yarn add --save css-loader and yarn add --save postcss-loader and no luck. I’ve tried remove node_modules and the yarn lock file and reinstalling but no luck.
It is likely an issue with your PostCSS plugin ordering.
Remove require('postcss-purgecss-laravel') – it’s not needed.
Remove the css-loader and postcss-loader you added – these will always be automatically installed/handled by Mix as needed. If you get an error message implying you should install them, something else is wrong.
Remove require('autoprefixer') – Mix includes this automatically.
Oh – and make sure you remove the Bootstrap imports in your app.css as they appear to be in your error log. FYI you do not have to use PostCSS with Tailwind – as someone who personally went down the PostCSS rabbit hole – I’d just stick with SCSS. Nested imports are too powerful to pass up.
For those of us that use SCSS it appears that mix has an issue with tailwinds (https://github.com/bholloway/resolve-url-loader/issues/28) that requires me to disable processCssUrls, it this a non-issue out of the box with Sage 10 or, when not of my own doing, something I need to be aware of in the Sage 10 workflow?