Commit de08808d authored by Tim's avatar Tim

feat: added purge support updated readme

parent 1cbd1cdf
......@@ -8,22 +8,82 @@ Uses postcss under the hood.
`npm install frets-styles-generator --save-dev`
And here is more recommended starter packages with common postcss pluugins, basecss library, and support for @import.
`npm install postcss-cli postcss-import postcss-preset-enc purgecss purge-css-from-frets cssnano basscss basscss-addons basscss-basic -D`
## Usage
`node node_modules/.bin/frets-styles-generator`
`npx frets-styles-generator`
The first argument you pass to the program will be the directory to scan for CSS files. It defaults to "./src" if you leave the argument out. Each CSS file that is found will be run through postcss (utilizing the [postcss-import](https://github.com/postcss/postcss-import) plugin by default) and then turned into a .ts file like [orginialFilename-styles.ts] based on the template specified. The default template is for [maquette](https://github.com/AFASSoftware/maquette) hyperscript functions.
Optionally pass this argument `-t '[path to custom template.js file]'` to specify a custom template.
Used in conjunction with FRETS and/or another hyperscript implementation. This particular template is specifically for the Maquette hyperscript implementation. Meaning it outputs a ts file that expects maquette to be available for import, so you will need 'maquette' in your project as a dependency.
## Other Options
Includes an optional watch flag `-w`.
Includes an options flag `-o` which will overwrite the original css file using the postcss-import plugin.
Used in conjunction with FRETS and/or another hyperscript implementation. This particular template is specifically for the Maquette hyperscript implementation. Meaning it outputs a ts file that expects maquette to be available for import, so you will need 'maquette' in your project as a dependency.
Setting the `-p` or `--purge` flag will allow the use of purgecss.
## Purging unused CSS
The generation of the typescript class suffers from the same inefficiency as atomic CSS. It includes a bunch of members that you may not be currently using in your actual source code. The atomic CSS people have found that using [purgecss](https://www.purgecss.com/) will greatly reduce file size by scanning your source code files for classnames that are used and only including those selectors in the final css outoput.
We can use the same technology for two purposes in FRETS. First, we configure postcss to scan our `src/**/.ts` files with the custom extractor [purgecss-from-frets](https://www.npmjs.com/package/purgecss-from-frets) and when we use PostCSS to compile browser-ready css we will get only the selectors that are neccessary!
Here's my sample postcss config.
```js
const postcssPresetEnv = require('postcss-preset-env');
var atImport = require("postcss-import");
var purgecss = require("@fullhuman/postcss-purgecss");
var purgeFromFrets = require("purgecss-from-frets");
module.exports = {
plugins: [
atImport(),
postcssPresetEnv({
stage: 1,
browsers: 'last 2 versions'
}),
purgecss({
content: ['./src/components/**/*.ts'],
extractors: [
{ extractor: purgeFromFrets, extensions: ["ts"] }
],
whitelist: ['html', 'body', 'input', 'button', 'select'],
whitelistPatterns: [/icon/, /green/],
rejected: true
})
// cssnano({
// preset: 'default',
// })
],
input: 'src/base.css',
dir: 'dist'
}
```
Now to solve the other half of the problem. Normally when frets-styles-generator analyzes your source css file it purposefully removes the purgecss plugin so that you have access to the entire set of class names from your css file when writing typscript code.
But, during your build script you can actually re-generate the `*-styles.ts` files with the `-p` flag to allow purgecss to remove unused selectors from your typescript class too! This will significantly decrease the size of your `*-styles.ts` files before they get compiled into final javascript bundles by webpack.
Here's a sample build script from my package.json.
```json
"build:prod": "frets-styles-generator src/base.css src/base-styles.ts -p && cross-env NODE_ENV=production webpack -p && npm run css && npm run css:minify",
```
I find it especially useful for rapid prototyping if you point it at [BaseCSS](https://github.com/basscss/bassplate) or [tachyons](http://tachyons.io/) because then you have a chainable typescript method for every "atomic" css class.
## Custom Templates
See the [current maquette template](https://gitlab.com/FRETS/frets-styles-generator/blob/master/src/templates/maquette.ts) for an example.
It should be possible to build templates for using the preact, react, or vue hyperscript functions.
This diff is collapsed.
{
"name": "frets-styles-generator",
"version": "0.2.0",
"version": "1.0.0",
"description": "Tool that genreates a typescript class for FRETS based on a CSS file",
"main": "build/main/index.js",
"typings": "build/main/index.d.ts",
......
......@@ -34,6 +34,12 @@ program
"-t, --template <path>",
"specify a custom template file [path to a js module]",
)
.option(
"-p, --purge",
`Allow purgecss in your custom postcss.config.js to purge the output files.
Default is to skip purgecss plugin if it's in your project postcss.config`,
false,
)
// .option('-v, --verbose', 'A value that can be increased', increaseVerbosity, 0)
.parse(process.argv);
......@@ -73,18 +79,22 @@ if (!fs.existsSync(postCssConfigPath)) {
}
customPlugins = require(postCssConfigPath).plugins;
if (customPlugins) {
if (customPlugins["import"]) {
delete customPlugins["import"];
}
if (customPlugins["atImport"]) {
delete customPlugins["atImport"];
}
if (customPlugins["importer"]) {
delete customPlugins["importer"];
}
const removeThesePlugins: string[] = ["postcss-import"];
if (!program.purge) {
// we don't want purge to run by default
removeThesePlugins.push("postcss-plugin-purgecss");
}
customPlugins = customPlugins.filter((p) => {
if (p && p.postcssPlugin && removeThesePlugins.includes(p.postcssPlugin)) {
console.log("removing ", p.postcssPlugin);
return false;
}
return true;
});
// console.log(customPlugins);
function readFile(input: string, output: string) {
console.log("reading " + input);
const dirparts = input.split("/");
......@@ -104,7 +114,7 @@ function readFile(input: string, output: string) {
// const opts = Object.assign(customConfigObject || {}, { root: inputPath });
// console.log("Using Config: ", opts);
postcss([...customPlugins, importer({ root: inputPath })])
postcss([importer({ root: inputPath }), ...customPlugins])
.process(data.toString(), {
from: inputPath,
})
......
{
"extends": "./config/tsconfig.strict", // also available: "./config/tsconfig.strict"
"compilerOptions": {
"target": "es6",
"target": "es2017",
"outDir": "build/main",
// "rootDir": "src",
"moduleResolution": "node",
......@@ -16,7 +16,7 @@
"allowSyntheticDefaultImports": false,
"noImplicitAny": false,
"lib" : [
"es6",
"es2017",
"dom"
],
"types" : [
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment