Merge pull request #7 from mpech/main

enable customAtRules to be given in options

Readme.md

@@ -46,6 +46,7 @@ build({
                 // Add your own or other plugins in the "visitor" section see
                 // https://lightningcss.dev/transforms.html
                 // visitor: myLightningcssPlugin(),
+                // customAtRules: { myLigningCssRule1: {...} }
                 targets: {
                     chrome: 80 // aligns somewhat to es2020
                 },
@@ -77,3 +78,5 @@ If this is not the case, and they end with `.css` while you still want to exclud
 includeFilter: /\.css$/,
 excludeFilter: /@fortawesome\/fontawesome-svg-core\/|my-normal-css-file\.css|normalize\.css/,
 ```
+
+### ``

index.js

@@ -12,6 +12,7 @@ const { dirname, join } = require("path");
  * @param {import("lightningcss").TransformOptions["visitor"]=} options.visitor
  * @param {import("lightningcss").TransformOptions["targets"]=} options.targets
  * @param {import("lightningcss").TransformOptions["drafts"]=} options.drafts
+ * @param {import("lightningcss").TransformOptions["customAtRules"]=} options.customAtRules
  * @param {import("lightningcss").CSSModulesConfig["pattern"]=} options.cssModulesPattern
  * @param {import("lightningcss").CSSModulesConfig=} options.cssModules
  * @return {import("esbuild").Plugin}
@@ -57,6 +58,7 @@ const cssModules = (options = {}) => {
                     targets: options.targets,
                     drafts: options.drafts,
                     visitor: options.visitor,
+                    customAtRules: options.customAtRules,
                     // this way the correct relative path for the source map will be generated ;)
                     projectRoot: join(initialOptions.absWorkingDir || process.cwd(), initialOptions.outdir)
                 });