Reluctantly support compiling CSS via webpack

Author: Jannik Zschiesche

CHANGELOG.md

@@ -37,6 +37,7 @@
 *   (improvement) Build TypeScript for the `esnext` module system, that (amongst other things) allows to use `import()`.
 *   (bug) Compile every entry into a separate directory, to avoid issues with the clean plugin.
 *   (bc) Now only specific modules in `node_modules` are transformed. You need to set your packages explicity via `.compileNpmPackages()`.
+*   (feature) Even if not recommended (use SCSS!), we now support compiling CSS via webpack (not as entry point though). The CSS will be injected into the head dynamically.
 
 
 8.1.0

package.json

@@ -37,13 +37,14 @@
         "eslint-plugin-react": "^7.17.0",
         "eslint-plugin-react-hooks": "^2.3.0",
         "fs-extra": "^8.1.0",
-        "ignore-loader": "^0.1.2",
         "kaba-babel-preset": "^4.1.1",
         "kleur": "^3.0.3",
+        "postcss-loader": "^3.0.0",
         "pretty-hrtime": "^1.0.3",
         "progress-bar-webpack-plugin": "^2.1.0",
         "raw-loader": "^4.0.0",
         "sade": "^1.7.0",
+        "style-loader": "^1.1.3",
         "terser-webpack-plugin": "^2.3.2",
         "ts-loader": "^6.2.1",
         "typescript": "^3.7.4",

src/Kaba.ts

@@ -13,6 +13,7 @@ const { CleanWebpackPlugin } = require('clean-webpack-plugin');
 
 const PACKAGE_MATCHER = /\/node_modules\/(?<package>[^\/]+)\//;
 interface CompiledNpmPackagesMapping {[name: string]: true}
+interface PostCssLoaderOptions {[key: string]: any}
 
 interface Entries
 {
@@ -75,6 +76,7 @@ export class Kaba
         mojave: true,
         '@mayd': true,
     };
+    private postCssLoaderOptions: PostCssLoaderOptions = {};
 
 
     /**
@@ -252,6 +254,16 @@ export class Kaba
     }
 
 
+    /**
+     * Sets the loader options for the postcss loader
+     */
+    public setPostCssLoaderOptions (options: PostCssLoaderOptions): this
+    {
+        this.postCssLoaderOptions = options;
+        return this;
+    }
+
+
     /**
      * Returns the kaba config
      *