Upload Triggers too Early in Build Process about s3-plugin-webpack

[MikaAK]

Awesome, thanks for more info. I've merged it in and will draft a release tonight 😄
Thanks for your work 🙏

[caseybienvenu]

I am also experiencing a similar problem. I have one JS file generated using mix.scripts that does not get transferred to S3 the first time the S3 plugin runs. Other files are transferred properly.

Interestingly, when I run a 2nd time, that missing JS file is transferred properly.

Also using s3-webpack-plugin version 1.0.3.

I forgot to say, if you need any additional information, or more non-Laravel Mix examples then let me know and I can expand further, and give some code examples. I wanted to keep the description brief in the first instance.

[MikaAK]

You can fix this by using the directory parameter to specify the build directory. Unfortunately, I don't think making changes to suit larvel is a good idea!

Thank you for your prompt response.

As mentioned, this is not relevant to just those using Laravel Mix, it just so happens that the examples I have provided are related to it.

I tested out every available parameter and option before posting as I wanted to ensure I had tried everything. Not to mention, my implementation is already using the directory parameter.

Surely just updating the event to trigger once the compilation is complete is a good thing to do regardless?

Thank you so much!!! :-D

Hi Mika,

Any update on the release? I can see the build is failing, is there anything I can help with?

[MikaAK]

The tests are failing and I'm not sure why, I was inclined to think it a config on aws issue but some fail others don't, gonna try reverting and testing, if it doesn't fail we'll need to fix tests before launching this

Okay, thanks Mika, keep me updated :-D

[selected-pixel-jameson]

Also having the exact same issue.