【英】React v16.8发布

作者: Dan Abramov

前言

这个春节不简单啊,大年初一Vue2.6发布,昨日React 16.8发布。

正文从这开始~~

react v16.8.0正式发布,这个版本包含了React Hook。也是React Hook正式发行的版本。

With React 16.8, React Hooks are available in a stable release!

What Are Hooks?

Hooks let you use state and other React features without writing a class. You can also build your own Hooks to share reusable stateful logic between components.

If you’ve never heard of Hooks before, you might find these resources interesting:

No Big Rewrites

We don’t recommend rewriting your existing applications to use Hooks overnight. Instead, try using Hooks in some of the new components, and let us know what you think. Code using Hooks will work side by side with existing code using classes.

Can I Use Hooks Today?

Yes! Starting with 16.8.0, React includes a stable implementation of React Hooks for:

Note that to enable Hooks, all React packages need to be 16.8.0 or higher. Hooks won’t work if you forget to update, for example, React DOM.

React Native will support Hooks in the 0.59 release.

Tooling Support

React Hooks are now supported by React DevTools. They are also supported in the latest Flow and TypeScript definitions for React. We strongly recommend enabling a new lint rule called eslint-plugin-react-hooks to enforce best practices with Hooks. It will soon be included into Create React App by default.

What’s Next

We described our plan for the next months in the recently published React Roadmap.

Note that React Hooks don’t cover all use cases for classes yet but they’re very close. Currently, only getSnapshotBeforeUpdate() and componentDidCatch() methods don’t have equivalent Hooks APIs, and these lifecycles are relatively uncommon. If you want, you should be able to use Hooks in most of the new code you’re writing.

Even while Hooks were in alpha, the React community created many interesting examples and recipes using Hooks for animations, forms, subscriptions, integrating with other libraries, and so on. We’re excited about Hooks because they make code reuse easier, helping you write your components in a simpler way and make great user experiences. We can’t wait to see what you’ll create next!

Testing Hooks

We have added a new API called ReactTestUtils.act() in this release. It ensures that the behavior in your tests matches what happens in the browser more closely. We recommend to wrap any code rendering and triggering updates to your components into act() calls. Testing libraries can also wrap their APIs with it (for example, react-testing-library’s render and fireEvent utilities do this).

For example, the counter example from this page can be tested like this:

import React from 'react';
import ReactDOM from 'react-dom';
import { act } from 'react-dom/test-utils';
import Counter from './Counter';
let container;
beforeEach
(() => {
 container
= document.createElement('div');
 document
.body.appendChild(container);
});
afterEach
(() => {
 document
.body.removeChild(container);
 container
= null;
});
it
('can render and update a counter', () => {
 
// Test first render and effect
 act
(() => {
   
ReactDOM.render(<Counter />, container);
 
});
 
const button = container.querySelector('button');
 
const label = container.querySelector('p');
 expect
(label.textContent).toBe('You clicked 0 times');
 expect
(document.title).toBe('You clicked 0 times');
 
// Test second render and effect
 act
(() => {
   button
.dispatchEvent(new MouseEvent('click', {bubbles: true}));
 
});
 expect
(label.textContent).toBe('You clicked 1 times');
 expect
(document.title).toBe('You clicked 1 times');
});

The calls to act() will also flush the effects inside of them.

If you need to test a custom Hook, you can do so by creating a component in your test, and using your Hook from it. Then you can test the component you wrote.

To reduce the boilerplate, we recommend using react-testing-library which is designed to encourage writing tests that use your components as the end users do.

Thanks

We’d like to thank everybody who commented on the Hooks RFC for sharing their feedback. We’ve read all of your comments and made some adjustments to the final API based on them.

Installation

React

React v16.8.0 is available on the npm registry.

To install React 16 with Yarn, run:

yarn add react@^16.8.0 react-dom@^16.8.0

To install React 16 with npm, run:

npm install --save react@^16.8.0 react-dom@^16.8.0

We also provide UMD builds of React via a CDN:

<script crossorigin src="https://unpkg.com/react@16/umd/react.production.min.js"></script>
<script crossorigin src="https://unpkg.com/react-dom@16/umd/react-dom.production.min.js"></script>

Refer to the documentation for detailed installation instructions.

ESLint Plugin for React Hooks

Note

As mentioned above, we strongly recommend using the eslint-plugin-react-hooks lint rule.

If you’re using Create React App, instead of manually configuring ESLint you can wait for the next version of react-scripts which will come out shortly and will include this rule.

Assuming you already have ESLint installed, run:

# npm
npm install eslint
-plugin-react-hooks@next --save-dev
# yarn
yarn add eslint
-plugin-react-hooks@next --dev

Then add it to your ESLint configuration:

{
 
"plugins": [
   
// ...
   
"react-hooks"
 
],
 
"rules": {
   
// ...
   
"react-hooks/rules-of-hooks": "error"
 
}
}

关于本文
作者:@Dan Abramov
原文:https://reactjs.org/blog/2019/02/06/react-v16.8.0.html

最后,为你推荐


【第1522期】Vue 2.6 发布了


【第1428期】React v16.7 "Hooks" - What to Expect