- Feb 2022
-
blog.codinghorror.com blog.codinghorror.com
-
Can't annotate the comments for some reason, so I am copying the below:
The Jerk talked about getting hit by a bus, etc. I said who cares about code if a guy’s in hospital or there’s a war, we’ve got better things to worry about than a few days of lost code.
I feel the pain. I do. I understand. I get scared. I want to check in early and often, but source control isn’t your personal unlimited undo. When I look at history I don’t want to see rubbish. I want to see snapshots of working code.
Don’t hold back, and don’t go dark, but use your f’ing head. It’s far better to locally integrate multiple times per day and merge back after a few days because guess what, no surprises.
-
- Jan 2021
-
-
6. Add Purgecss for unused CSS removal (optional) Add Purgecss to Sage. Once you’ve successfully added Purgecss, you will need to complete an addition step to make sure Purgecss can extract Tailwind’s classes properly. Luckily, Tailwind has a guide in their docs to add a custom Purgecss extractor.
Date: 28/01/2021
Had problem during purgecss installation in my project. Solved using:
yarn add --dev purgecss-webpack-plugin@0.23.0 glob-all
More info: Getting an error regarding webpack, during step 1 of adding purgecss ( https://roots.io/guides/removing-unused-css-with-purgecss-uncss-in-sage/ )
Solved using the command for yarn as given in here:
https://discourse.roots.io/t/removing-unused-css-with-purgecss-uncss/11586
That is :
yarn add --dev purgecss-webpack-plugin@0.23.0 glob-all
-