UnkownEndpoint error when trying to use plugin about s3-plugin-webpack

[MikaAK]

Thanks for the feedback. I'll try to get to fixing this soon. For now, I would downgrade unless necessary. I'm not actually 100% sure how the cloudfront invalidation actually works so I will have to do some research and figure out how best to get around this. @flipxfx may be able to guess on this right away though

[thescientist13]

Yeah, refactoring my build seems to have resolved my issue. Hope this can help someone else at least.

[aMoRRoMa]

I have same problem :(

[flippidippi]

Weird that the error is shown before as the invalidation happens after right? This error seems to be related to s3. andrewrk/node-s3-client#68 (comment)

[thescientist13]

Doing some more testing locally and I think I have narrowed down the issue to my usage of CopyWebpackPlugin with a large directory from node_modules for loading CKEditor as part of my Angular app's bundle. Without this in my common build, everything works with no error, including Cloudfront invalidation.

new CopyWebpackPlugin([{
  //TODO add using import?
  context: './node_modules/ckeditor/',
  from: '**/**',
  to: './assets/vendor/ckeditor/'
}]),

In reviewing options for optimizing the loading of ckeditor (which is about 15MB) I noticed a newer version ng2-ckeditor that was released that supports Angular's NgModule, which may provide a better bundling opportunity and reduce the dependency on CopyWebpackPlugin and greedy copying all files from that directory in node_modules.