[revelation]

I still remember the times when warning were actual likely mistakes in your code, not "we're adding some more churn, update your stuff until we churn more".

If you want people to always ignore warnings, this is how you go about it.

[acemarke]

Baloney. This is proper release management planning. People keep complaining that React is too big and needs to shrink down. They're planning to help address those complaints by removing pieces they no longer intend to maintain, or are not the primary usage going forward. So, they're putting out a minor release that will warn people these pieces are being removed, and then they'll be removed in the upcoming major release. Seems like the right approach to me.

[mtrpcic]

Yeah, these are basically Deprecation Warnings, which have been a standard part of good release management for a long time, across many projects in many industries.

[garfij]

> For each of these new deprecations, we've provided a codemod to automatically migrate your code. They are available as part of the react-codemod project.

They gave you tools to automatically fix any new warnings that came from this. I honestly don't know how they could have made it any easier.

[spion]

Unless you use typescript or coffeescript. In which case you're on your own.

[spion]

Interesting, I didn't expect a downvotes. If this is factually incorrect, please do point it out. I looked at the tool and it seems it only works on plan JS and Facebook's JS dialect (flowtype)

[tracker1]

Typescript doesn't do development vs. production builds?

[spion]

I don't see how thats relevant? The point is that the codemod tool doesn't work on TypeScript. So you still have to fix the warnings manually.

I don't think its too bad, just saying that the tool doesn't solve the problem for everyone.

[clay_to_n]

If you don't want to upgrade to React v16, why would you upgrade to React 15.5.0 (which includes the new warnings)?

[mparr4]

Only reason to upgrade is if you care about the specific bug fixes [1] or have your eye on React 16.

Not interested in either? Then don't upgrade.

[1] - fixes enumerated here: https://facebook.github.io/react/blog/2017/04/07/react-v15.5...