fix: use postcss-preset-env for processing new CSS syntax (#807)

apify · Jan 4, 2024 · 16d8355 · 16d8355
1 parent d5b9cc8
commit 16d8355
Show file tree

Hide file tree

Showing 4 changed files with 1,600 additions and 19 deletions.
diff --git a/apify-docs-theme/package.json b/apify-docs-theme/package.json
@@ -19,7 +19,7 @@
         "access": "public"
     },
     "dependencies": {
-        "@apify/docs-search-modal": "^1.0.24",
+        "@apify/docs-search-modal": "^1.0.25",
         "@docusaurus/theme-common": "^2.4.1",
         "@stackql/docusaurus-plugin-hubspot": "^1.1.0",
         "axios": "^1.4.0",

diff --git a/docusaurus.config.js b/docusaurus.config.js
@@ -1,3 +1,4 @@
+const postcssPreset = require('postcss-preset-env');
 const { config } = require('./apify-docs-theme');
 const { externalLinkProcessor } = require('./tools/utils/externalLink');
 const { collectSlugs } = require('./tools/utils/collectSlugs');
@@ -91,6 +92,13 @@ module.exports = {
                 sidebarPath: require.resolve('./sources/academy/sidebars.js'),
             },
         ],
+        () => ({
+            name: 'new-css-syntax',
+            configurePostCss(options) {
+                options.plugins.push(postcssPreset); // allow newest CSS syntax
+                return options;
+            },
+        }),
         // TODO this should be somehow computed from all the external sources
         // [
         //     '@docusaurus/plugin-client-redirects',