Incompatibility with webpack-manifest-plugin about autodll-webpack-plugin

[TomiHiltunen]

Same problem here.

[coagit]

In order to get around this issue you can put webpack-manifest-plugin as a plugin in the auto dll.
Just use a different name for the dll manifest so it won't overwrite your main manifest file.

...

plugins: [
  new AutoDllPlugin({
    entry: {...},
    plugins: [new WebpackManifestPlugin({fileName: 'dll.manifest.json'})]
  })
]

...

Then you will have two manifest files which can be merged somehow, or used separately.

[stephencookdev]

You can generate just 1 manifest file by adding a custom generate function

const seed = {};
const generate = (_, files) => files.reduce((_, { name, path }) => {
  // modify the shared seed object, so as to share it between the main and
  // DLL compiler instance
  seed[name] = path;
  return seed;
}),

module.exports = {
  plugins: [
    new WebpackManifestPlugin({
      generate,
      seed
    }),
    new AutoDllPlugin({
      plugins: [new WebpackManifestPlugin({
        generate,
        seed,
        fileName: '_throwaway.json'
      })]
    })
  ]
};

Still a bit hacky 😞 but generates 1 correct manifest file

In theory just doing the shared seed thing should solve the issue, but I'm guessing that something is causing the AutoDllPlugin's WebpackManifestPlugin instance to run first, but then output last (causing the staler manifest file to overwrite the newer file - hence the need for the _throwaway.json file)