Project breaking due to "Removed default export" about react-notifications-component

[teodosii]

The problem was that I updated the package to use the ts-loader in order to export all types & interfaces. Due to an ordering issue on the loaders it never passed through the babel-loader, and one of the issues I did notice was about the default export. Since I had already released and the release was in an error state, had to come up with a solution and the solution was to remove the default export.

I can add it back now since the loaders are set in the correct order now but I don't see the point in it.

So to answer your questions

1. Maybe. Or maybe not. The release was in an an error state so it had to be fixed on that 3.X.Y
2. Unfortunately if the release is in an error state, pretty much nothing except to downgrade or wait for the library maintainer to publish a new fix. Such things happen, it's a free software, I don't get paid to release it.