4.4.2 completely broken : dist deleted !

[cyrilletuzi]

dist folder is missing in 4.4.2 release, so it breaks every tools depending on this module !

@d3viant0ne

[ocombe]

I was gonna open an issue with this, please release a fix asap because it breaks @angular/cli :(

[stas-kh]

Guys, we need this fix asap, please

[antshc]

We have same problem, can you fix this?

[bubkoo]

Online waiting...

[ocombe]

In the mean time npm install -D copy-webpack-plugin@4.2.1 will fix the problem

[oleksandrstarov]

Please fix this asap, it is killing the deadline

[sokra]

Please fix this asap, it is killing the deadline

Chill down. It has been reported 5 minutes ago...

[alexander-akait]

Don't flood please, we will work on this

[Golodnyi]

guys, version 4.2.2, not 4.4.2

[joshwiens]

I know what he meant, fixed in 4.2.3

[joshwiens]

For all of you less the CLI group who has a legitimate gripe, you can simply pin a dependency if something like this happens and be less dramatic.

It's 04:00
It was broken for all of 9 minutes
If your deadline is being killed, there was a issue long before v4.2.2

Before you start spamming maintainers, bare in mind you can't even get a 10 minute turn around at a fast food restaurant. Be less spastic, you will live longer.

[ocombe]

And don't forget that pinning dependencies (manually, or with yarn) is the safest bet ;-)

[filipesilva]

@sokra @evilebottnawi @d3viant0ne thanks for the quick fix on this!

Wasn't expecting so many people to be affected in such a short period of time but if this affected you please remember that without using package-lock.json or yarn.lock you will will never ensure that your dependencies are the same between installs.

Bugs and bad releases unfortunately happen but there is nothing library maintainers can do to to truly prevent this from propagating. Pinning dependencies is not enough. It is up to you, as a consumer, to use dependency locks.