chore: remove unneeded webpackImporter option for example webpack con…

…figs
Financial-Times · Oct 14, 2024 · cf18e50 · cf18e50
1 parent a78b59c
commit cf18e50
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 8 deletions.
diff --git a/examples/ft-ui/webpack.config.js b/examples/ft-ui/webpack.config.js
@@ -13,10 +13,6 @@ module.exports = {
     new PageKitBasePlugin(),
     new PageKitJsPlugin(),
     new PageKitSassPlugin({
-      // Enabling webpackImporter because Sass itself can only resolve partial files based on the
-      // CWD and not relative to the current file being processed. This means Sass can't find the
-      // nested dependencies created when symlinking.
-      webpackImporter: true,
       includePaths: [path.resolve('../../node_modules')]
     })
   ]

diff --git a/examples/kitchen-sink/webpack.config.js b/examples/kitchen-sink/webpack.config.js
@@ -16,10 +16,6 @@ module.exports = {
     new PageKitJsPlugin(),
     new PageKitCodeSplittingPlugin(),
     new PageKitSassPlugin({
-      // Enabling webpackImporter because Sass itself can only resolve partial files based on the
-      // CWD and not relative to the current file being processed. This means Sass can't find the
-      // nested dependencies created when symlinking.
-      webpackImporter: true,
       includePaths: [path.resolve('../../node_modules')]
     })
   ]