Don't log outputPath

[stevenvachon]

It's not consistent with the rest of the webpack log:

                      Asset      Size          Chunks             Chunk Names
/project/build/legacyApp.js  4.11 MiB                  [emitted]  
                  ccApp.css  26.3 KiB           ccApp  [emitted]  ccApp
                   ccApp.js   117 KiB           ccApp  [emitted]  ccApp
         ccDesignSystem.css  60.6 KiB  ccDesignSystem  [emitted]  ccDesignSystem
          ccDesignSystem.js  1.63 MiB  ccDesignSystem  [emitted]  ccDesignSystem
                 ccUser.css    27 KiB          ccUser  [emitted]  ccUser
                  ccUser.js  50.1 KiB          ccUser  [emitted]  ccUser
                 common.css   678 KiB          common  [emitted]  common
                  common.js  11.7 MiB          common  [emitted]  common

[stevenvachon]

Actually, this was caused because outputPath was doubled up somehow due to it having the same value as webpack's output.path. Is this a bug, or expected behaviour?

[scriptin]

@stevenvachon Had the same problem.

The solution is:

1. Specify output.path in Webpack's config
2. Don't specify outputPath in this plugin's config

The path you put in outputPath of this plugin is relative to Webpack's output.path (they are probably combined via path.resolve()). This means that if you put the same path in both output.path and outputPath you will have those "doubled up" paths. I believe this is intended, but the docs of this plugin don't describe this behavior.

This is also why you see your outputPath in logs, because in your configuration their parent directories are not the same as Webpack's output.path. If you remove this setting (the 2nd step above), you'll see what you expect.