@ -13,7 +13,11 @@ Read on to learn more about the release.
## Official Context API
For many years, React has offered an experimental API for context. Although it was a powerful tool, our advice was mostly to [avoid using it](/docs/context.html#why-not-to-use-context) because of potential problems with the API. We've always intended to replace the experimental API with a better one, and as of version 16.3- we've finally done that!
For many years, React has offered an experimental API for context. Although it was a powerful tool, our advice was mostly to [avoid using it](/docs/context.html#why-not-to-use-context) because of potential problems with the API. We've always intended to replace the experimental API with a better one, and as of version 16.3 the new API is available!
> **Note**
>
> The old context API will keep working for all React 16 minor releases, so you will have time to migrate.
[Learn more about the new context API here.](#)
@ -44,11 +48,11 @@ We recognize that this change will impact many existing components. (At Facebook
> **Note:**
>
> Deprecation warnings will be enabled in version 16.4, **but the deprecated lifecycles will continue to work until version 17**.
> Deprecation warnings will be enabled in version 16.4, **but the legacy lifecycles will continue to work until version 17**.
>
> After version 17, it will still be possible to use them, but they will be aliased with an "UNSAFE_" prefix to indicate that they might cause issues. We have also prepared an [automated script to rename them](https://github.com/reactjs/react-codemod#rename-unsafe-lifecycles) in existing code.
We are also adding a new static lifecycle, `getDerivedStateFromProps`, as a safer alternative to the deprecated`componentWillReceiveProps`.
We are also adding a new static lifecycle, `getDerivedStateFromProps`, as a safer alternative to the legacy`componentWillReceiveProps`.
[Learn more about these lifecycle changes here.](#)
Brian Vaughn
7 years ago