[chore] upgrades html-minifier-terser@5.0.0 -> 6.0.2

[gabrielcsapo]

Summary

fixes #1687.

Updates the snapshots to reflect the terser upgrade.

[gabrielcsapo]

@jantimon I will have a follow up PR to make these fixtures snapshots as this would have been easier to run jest -u instead of having to update the fixtures manually if that okay with you?

[jantimon]

You can rebuild all examples with npm run rebuild-examples

Snapshots are way harder to read

[gabrielcsapo]

I will run that to make sure I got everything! @jantimon

Is there anything else I should do before we can merge?

[jantimon]

We don't need async await to return the promise.
Can you please revert those two changes?

[jantimon]

@gabrielcsapo did you already have time to look into my feedback? :)

[gabrielcsapo]

@jantimon just updated the PR based on the feedback.

[gabrielcsapo]

@jantimon kindly bumping this.

[jantimon]

thanks @gabrielcsapo

[jantimon]

released as 5.4.0

[jantimon]

@gabrielcsapo your changes break the build pipelines - could you please take a look what’s wrong?

[gabrielcsapo]

Yes, I’ll check today.

…

On Sat, Oct 16, 2021 at 1:42 AM Jan Nicklas ***@***.***> wrote: @gabrielcsapo <https://github.com/gabrielcsapo> your changes break the build pipelines - could you please take a look what’s wrong? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1688 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAOE2WYFTRFGWVZ2ILABIOLUHE3ITANCNFSM5FAXH7LA> .

[gabrielcsapo]

@jantimon there seems to be a race condition with checking the contents of the files on disk and starting a new test. It might make sense to have each test output to a specific directory on disk to avoid collisions. I am not seeing this same issue locally, so it will be hard to debug to be for sure.

Another option is using snapshots as they are in memory and won't have collision issues.