From cf18e50d6db4e46b88421c6de6d7c4b55f659d3b Mon Sep 17 00:00:00 2001 From: Kara Brightwell Date: Mon, 14 Oct 2024 11:20:54 +0100 Subject: [PATCH] chore: remove unneeded webpackImporter option for example webpack configs --- examples/ft-ui/webpack.config.js | 4 ---- examples/kitchen-sink/webpack.config.js | 4 ---- 2 files changed, 8 deletions(-) diff --git a/examples/ft-ui/webpack.config.js b/examples/ft-ui/webpack.config.js index 96a1d8932..cd733da75 100644 --- 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 index b39ef6756..3e4239d39 100644 --- 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')] }) ]