Output path not being created recursively

[filipesilva]

Heya,

If the webpack configuration has a deep output path that doesn't currently exist, license-webpack-plugin will fail at mkdirSync (angular/angular-cli#7203).

Webpack itself is ok with creating this path and putting files there though. Perhaps compilation.assets could be used instead of mkdirSync? There's an example at https://github.com/webpack/docs/wiki/how-to-write-a-plugin#a-simple-example where they do that. That way Webpack itself would take care of outputting it.

[xz64]

In order to get access to the compilation object I will need to refactor the plugin to hook into the emit phase of webpack. I will try out your suggestion.

[xz64]

@filipesilva I have pushed some updates to the dev branch. Please try it out and let me know if you run into any issues. There is a migration guide at MIGRATION.md for some breaking changes.

[filipesilva]

Hi @xz64, I can confirm that using the dev branch this bug does not manifest anymore.