fix: publicpath-function test demonstrates purpose

With output of the CSS into a nested folder the computation of the relative publicPath makes sense.
webpack-contrib · Apr 5, 2019 · 9ef1de0 · 9ef1de0
1 parent 0f76012
commit 9ef1de0
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 2 deletions.
diff --git a/...ses/publicpath-function/expected/main.css → ...icpath-function/expected/nested/style.css b/...ses/publicpath-function/expected/main.css → ...icpath-function/expected/nested/style.css
diff --git a/test/cases/publicpath-function/index.js b/test/cases/publicpath-function/index.js
diff --git a/test/cases/publicpath-function/webpack.config.js b/test/cases/publicpath-function/webpack.config.js
@@ -2,7 +2,10 @@ const Self = require('../../../');
 const path = require('path')
 
 module.exports = {
-  entry: './index.js',
+  entry: {
+    // Specific CSS entry point, with output to a nested folder
+    'nested/style': './nested/style.css',
+  },
   module: {
     rules: [
       {
@@ -11,6 +14,7 @@ module.exports = {
           {
             loader: Self.loader,
             options: {
+              // Compute publicPath relative to the CSS output
               publicPath: (resourcePath, context) => path.relative(path.dirname(resourcePath), context) + '/',
             }
           },