diff --git a/content/community/conferences.md b/content/community/conferences.md index e138b119a..833e44c40 100644 --- a/content/community/conferences.md +++ b/content/community/conferences.md @@ -52,10 +52,10 @@ June 21, 2019 Chicago, Illinois USA [Website](https://reactloop.com) - [Twitter](https://twitter.com/ReactLoop) -### React Week '19 {#RWNY19} -July 15-21, 2019. New York City, USA +### React Rally 2019 +August 22-23, 2019. Salt Lake City, USA. -[Website](https://reactweek.nyc) - [Twitter](https://twitter.com/ReactWeek) +[Website](https://www.reactrally.com/) - [Twitter](https://twitter.com/ReactRally) - [Instagram](https://www.instagram.com/reactrally/) ### ComponentsConf 2019 {#componentsconf-2019} September 6, 2019 in Melbourne, Australia diff --git a/content/community/meetups.md b/content/community/meetups.md index d397a4535..8bd1155d0 100644 --- a/content/community/meetups.md +++ b/content/community/meetups.md @@ -88,6 +88,7 @@ Do you have a local React.js meetup? Add it here! (Please keep the list alphabet ## Pakistan {#pakistan} * [Karachi](https://www.facebook.com/groups/902678696597634/) +* [Lahore](https://www.facebook.com/groups/ReactjsLahore/) ## Peru {#peru} * [Lima](https://www.meetup.com/ReactJS-Peru/) @@ -130,8 +131,8 @@ Do you have a local React.js meetup? Add it here! (Please keep the list alphabet * [New York, NY - ReactJS](https://www.meetup.com/NYC-Javascript-React-Group/) * [New York, NY - React Ladies](https://www.meetup.com/React-Ladies/) * [New York, NY - React Native](https://www.meetup.com/React-Native-NYC/) -* [New York, NY - ReactNYC](https://www.meetup.com/ReactNYC/) * [Palo Alto, CA - React Native](https://www.meetup.com/React-Native-Silicon-Valley/) +* [Philadelphia, PA - ReactJS](https://www.meetup.com/RQ-React/) * [Phoenix, AZ - ReactJS](https://www.meetup.com/ReactJS-Phoenix/) * [Pittsburgh, PA - ReactJS/React Native](https://www.meetup.com/ReactPgh/) * [Portland, OR - ReactJS](https://www.meetup.com/Portland-ReactJS/) diff --git a/content/docs/hooks-faq.md b/content/docs/hooks-faq.md index 4ffc63eac..e748ac6c9 100644 --- a/content/docs/hooks-faq.md +++ b/content/docs/hooks-faq.md @@ -18,6 +18,7 @@ prev: hooks-reference.html ).join('\n') --> +<<<<<<< HEAD * [Внедрение хуков](#adoption-strategy) * [В какой версии React появились хуки?](#which-versions-of-react-include-hooks) * [Нужно ли переписать все мои классовые компоненты?](#do-i-need-to-rewrite-all-my-class-components) @@ -61,6 +62,52 @@ prev: hooks-reference.html ### В какой версии React появились хуки? {#which-versions-of-react-include-hooks} Начиная с релиза 16.8.0, React включает в себя стабильную реализацию хуков для: +======= +* **[Adoption Strategy](#adoption-strategy)** + * [Which versions of React include Hooks?](#which-versions-of-react-include-hooks) + * [Do I need to rewrite all my class components?](#do-i-need-to-rewrite-all-my-class-components) + * [What can I do with Hooks that I couldn't with classes?](#what-can-i-do-with-hooks-that-i-couldnt-with-classes) + * [How much of my React knowledge stays relevant?](#how-much-of-my-react-knowledge-stays-relevant) + * [Should I use Hooks, classes, or a mix of both?](#should-i-use-hooks-classes-or-a-mix-of-both) + * [Do Hooks cover all use cases for classes?](#do-hooks-cover-all-use-cases-for-classes) + * [Do Hooks replace render props and higher-order components?](#do-hooks-replace-render-props-and-higher-order-components) + * [What do Hooks mean for popular APIs like Redux connect() and React Router?](#what-do-hooks-mean-for-popular-apis-like-redux-connect-and-react-router) + * [Do Hooks work with static typing?](#do-hooks-work-with-static-typing) + * [How to test components that use Hooks?](#how-to-test-components-that-use-hooks) + * [What exactly do the lint rules enforce?](#what-exactly-do-the-lint-rules-enforce) +* **[From Classes to Hooks](#from-classes-to-hooks)** + * [How do lifecycle methods correspond to Hooks?](#how-do-lifecycle-methods-correspond-to-hooks) + * [How can I do data fetching with Hooks?](#how-can-i-do-data-fetching-with-hooks) + * [Is there something like instance variables?](#is-there-something-like-instance-variables) + * [Should I use one or many state variables?](#should-i-use-one-or-many-state-variables) + * [Can I run an effect only on updates?](#can-i-run-an-effect-only-on-updates) + * [How to get the previous props or state?](#how-to-get-the-previous-props-or-state) + * [Why am I seeing stale props or state inside my function?](#why-am-i-seeing-stale-props-or-state-inside-my-function) + * [How do I implement getDerivedStateFromProps?](#how-do-i-implement-getderivedstatefromprops) + * [Is there something like forceUpdate?](#is-there-something-like-forceupdate) + * [Can I make a ref to a function component?](#can-i-make-a-ref-to-a-function-component) + * [How can I measure a DOM node?](#how-can-i-measure-a-dom-node) + * [What does const [thing, setThing] = useState() mean?](#what-does-const-thing-setthing--usestate-mean) +* **[Performance Optimizations](#performance-optimizations)** + * [Can I skip an effect on updates?](#can-i-skip-an-effect-on-updates) + * [Is it safe to omit functions from the list of dependencies?](#is-it-safe-to-omit-functions-from-the-list-of-dependencies) + * [What can I do if my effect dependencies change too often?](#what-can-i-do-if-my-effect-dependencies-change-too-often) + * [How do I implement shouldComponentUpdate?](#how-do-i-implement-shouldcomponentupdate) + * [How to memoize calculations?](#how-to-memoize-calculations) + * [How to create expensive objects lazily?](#how-to-create-expensive-objects-lazily) + * [Are Hooks slow because of creating functions in render?](#are-hooks-slow-because-of-creating-functions-in-render) + * [How to avoid passing callbacks down?](#how-to-avoid-passing-callbacks-down) + * [How to read an often-changing value from useCallback?](#how-to-read-an-often-changing-value-from-usecallback) +* **[Under the Hood](#under-the-hood)** + * [How does React associate Hook calls with components?](#how-does-react-associate-hook-calls-with-components) + * [What is the prior art for Hooks?](#what-is-the-prior-art-for-hooks) + +## Adoption Strategy {#adoption-strategy} + +### Which versions of React include Hooks? {#which-versions-of-react-include-hooks} + +Starting with 16.8.0, React includes a stable implementation of React Hooks for: +>>>>>>> d0f2db967a38e358bd59c65e981862cdf38f3d0b * React DOM * React DOM Server @@ -454,7 +501,65 @@ function ScrollView({row}) { Несмотря на то, что вам не понадобится это часто, вы можете предоставить некоторые императивные методы родительскому компоненту, используя хук [`useImperativeHandle`](/docs/hooks-reference.html#useimperativehandle). +<<<<<<< HEAD ### Что значит `const [thing, setThing] = useState()`? {#what-does-const-thing-setthing--usestate-mean} +======= +### How can I measure a DOM node? {#how-can-i-measure-a-dom-node} + +In order to measure the position or size of a DOM node, you can use a [callback ref](/docs/refs-and-the-dom.html#callback-refs). React will call that callback whenever the ref gets attached to a different node. Here is a [small demo](https://codesandbox.io/s/l7m0v5x4v9): + +```js{4-8,12} +function MeasureExample() { + const [height, setHeight] = useState(0); + + const measuredRef = useCallback(node => { + if (node !== null) { + setHeight(node.getBoundingClientRect().height); + } + }, []); + + return ( + <> +

Hello, world

+

The above header is {Math.round(height)}px tall

+ + ); +} +``` + +We didn't choose `useRef` in this example because an object ref doesn't notify us about *changes* to the current ref value. Using a callback ref ensures that [even if a child component displays the measured node later](https://codesandbox.io/s/818zzk8m78) (e.g. in response to a click), we still get notified about it in the parent component and can update the measurements. + +Note that we pass `[]` as a dependency array to `useCallback`. This ensures that our ref callback doesn't change between the re-renders, and so React won't call it unnecessarily. + +If you want, you can [extract this logic](https://codesandbox.io/s/m5o42082xy) into a reusable Hook: + +```js{2} +function MeasureExample() { + const [rect, ref] = useClientRect(); + return ( + <> +

Hello, world

+ {rect !== null && +

The above header is {Math.round(rect.height)}px tall

+ } + + ); +} + +function useClientRect() { + const [rect, setRect] = useState(null); + const ref = useCallback(node => { + if (node !== null) { + setRect(node.getBoundingClientRect()); + } + }, []); + return [rect, ref]; +} +``` + + +### What does `const [thing, setThing] = useState()` mean? {#what-does-const-thing-setthing--usestate-mean} +>>>>>>> d0f2db967a38e358bd59c65e981862cdf38f3d0b Если вы не знакомы с этим синтаксисом, ознакомьтесь с [объяснением](/docs/hooks-state.html#tip-what-do-square-brackets-mean) в документации хука состояния. @@ -857,8 +962,13 @@ function Form() { const [text, updateText] = useState(''); const textRef = useRef(); +<<<<<<< HEAD useLayoutEffect(() => { textRef.current = text; // Записать в реф +======= + useEffect(() => { + textRef.current = text; // Write it to the ref +>>>>>>> d0f2db967a38e358bd59c65e981862cdf38f3d0b }); const handleSubmit = useCallback(() => { @@ -898,7 +1008,7 @@ function useEventCallback(fn, dependencies) { throw new Error('Невозможно вызвать обработчик события во время рендера.'); }); - useLayoutEffect(() => { + useEffect(() => { ref.current = fn; }, [fn, ...dependencies]); diff --git a/content/docs/hooks-reference.md b/content/docs/hooks-reference.md index 1029e0646..abbfa273c 100644 --- a/content/docs/hooks-reference.md +++ b/content/docs/hooks-reference.md @@ -96,6 +96,8 @@ const [state, setState] = useState(() => { Если вы обновите состояние хука тем же значением, что и текущее состояние, React досрочно выйдет из хука без повторного рендера дочерних элементов и запуска эффектов. (React использует [алгоритм сравнения `Object.is`](https://developer.mozilla.org/ru/docs/Web/JavaScript/Reference/Global_Objects/Object/is#Description).) +Note that React may still need to render that specific component again before bailing out. That shouldn't be a concern because React won't unnecessarily go "deeper" into the tree. If you're doing expensive calculations while rendering, you can optimize them with `useMemo`. + ### `useEffect` {#useeffect} ```js @@ -171,12 +173,32 @@ useEffect( ### `useContext` {#usecontext} ```js -const context = useContext(Context); +const value = useContext(MyContext); ``` +<<<<<<< HEAD Принимает объект контекста (значение, возвращённое из `React.createContext`) и возвращает текущее значение контекста, как указано ближайшим поставщиком контекста для данного контекста. Когда провайдер обновляется, этот хук инициирует повторный рендер с последним значением контекста. +======= +Accepts a context object (the value returned from `React.createContext`) and returns the current context value for that context. The current context value is determined by the `value` prop of the nearest `` above the calling component in the tree. + +When the nearest `` above the component updates, this Hook will trigger a rerender with the latest context `value` passed to that `MyContext` provider. + +Don't forget that the argument to `useContext` must be the *context object itself*: + + * **Correct:** `useContext(MyContext)` + * **Incorrect:** `useContext(MyContext.Consumer)` + * **Incorrect:** `useContext(MyContext.Provider)` + +A component calling `useContext` will always re-render when the context value changes. If re-rendering the component is expensive, you can [optimize it by using memoization](https://github.com/facebook/react/issues/15156#issuecomment-474590693). + +>Tip +> +>If you're familiar with the context API before Hooks, `useContext(MyContext)` is equivalent to `static contextType = MyContext` in a class, or to ``. +> +>`useContext(MyContext)` only lets you *read* the context and subscribe to its changes. You still need a `` above in the tree to *provide* the value for this context. +>>>>>>> d0f2db967a38e358bd59c65e981862cdf38f3d0b ## Дополнительные хуки {#additional-hooks} @@ -283,6 +305,8 @@ function Counter({initialCount}) { Если вы вернёте то же значение из редюсера хука, что и текущее состояние, React выйдет без перерисовки дочерних элементов или запуска эффектов. (React использует [алгоритм сравнения Object.is](https://developer.mozilla.org/ru/docs/Web/JavaScript/Reference/Global_Objects/Object/is#Description).) +Note that React may still need to render that specific component again before bailing out. That shouldn't be a concern because React won't unnecessarily go "deeper" into the tree. If you're doing expensive calculations while rendering, you can optimize them with `useMemo`. + ### `useCallback` {#usecallback} ```js @@ -354,7 +378,20 @@ function TextInputWithFocusButton() { } ``` +<<<<<<< HEAD Обратите внимание, что `useRef()` полезен не только для атрибута `ref`. Он также [удобен для хранения любого изменяемого значения](/docs/hooks-faq.html#is-there-something-like-instance-variables) примерно так же, как вы используете поля экземпляров в классах. +======= +Essentially, `useRef` is like a "box" that can hold a mutable value in its `.current` property. + +You might be familiar with refs primarily as a way to [access the DOM](/docs/refs-and-the-dom.html). If you pass a ref object to React with `
`, React will set its `.current` property to the corresponding DOM node whenever that node changes. + +However, `useRef()` is useful for more than the `ref` attribute. It's [handy for keeping any mutable value around](/docs/hooks-faq.html#is-there-something-like-instance-variables) similar to how you'd use instance fields in classes. + +This works because `useRef()` creates a plain JavaScript object. The only difference between `useRef()` and creating a `{current: ...}` object yourself is that `useRef` will give you the same ref object on every render. + +Keep in mind that `useRef` *doesn't* notify you when its content changes. Mutating the `.current` property doesn't cause a re-render. If you want to run some code when React attaches or detaches a ref to a DOM node, you may want to use a [callback ref](/docs/hooks-faq.html#how-can-i-measure-a-dom-node) instead. + +>>>>>>> d0f2db967a38e358bd59c65e981862cdf38f3d0b ### `useImperativeHandle` {#useimperativehandle} @@ -387,7 +424,15 @@ FancyInput = forwardRef(FancyInput); > Совет > +<<<<<<< HEAD > Если вы переносите код из классового компонента, `useLayoutEffect` запускается в той же фазе, что и `componentDidMount` и `componentDidUpdate`, поэтому, если вы не уверены, какой хук эффект использовать, это, вероятно, наименее рискованно. +======= +> If you're migrating code from a class component, note `useLayoutEffect` fires in the same phase as `componentDidMount` and `componentDidUpdate`. However, **we recommend starting with `useEffect` first** and only trying `useLayoutEffect` if that causes a problem. +> +>If you use server rendering, keep in mind that *neither* `useLayoutEffect` nor `useEffect` can run until the JavaScript is downloaded. This is why React warns when a server-rendered component contains `useLayoutEffect`. To fix this, either move that logic to `useEffect` (if it isn't necessary for the first render), or delay showing that component until after the client renders (if the HTML looks broken until `useLayoutEffect` runs). +> +>To exclude a component that needs layout effects from the server-rendered HTML, render it conditionally with `showChild && ` and defer showing it with `useEffect(() => { setShowChild(true); }, [])`. This way, the UI doesn't appear broken before hydration. +>>>>>>> d0f2db967a38e358bd59c65e981862cdf38f3d0b ### `useDebugValue` {#usedebugvalue} diff --git a/content/docs/optimizing-performance.md b/content/docs/optimizing-performance.md index 900d595e6..34a77a7b2 100644 --- a/content/docs/optimizing-performance.md +++ b/content/docs/optimizing-performance.md @@ -430,6 +430,10 @@ x === z; // true В этом случае, поскольку после мутирования `x` возвращается новая ссылка, мы можем использовать строгое сравнение (в данном случае по ссылке) `(x === y)` для того, чтобы убедиться, что новое значение хранящееся в `y` отличается от исходного значения, хранящегося в `x`. +<<<<<<< HEAD Есть две другие библиотеки, которые могут помочь вам использовать иммутабельные данные: [seamless-immutable](https://github.com/rtfeldman/seamless-immutable) и [immutability-helper](https://github.com/kolodny/immutability-helper). +======= +Other libraries that can help use immutable data include [Immer](https://github.com/mweststrate/immer), [immutability-helper](https://github.com/kolodny/immutability-helper), and [seamless-immutable](https://github.com/rtfeldman/seamless-immutable). +>>>>>>> d0f2db967a38e358bd59c65e981862cdf38f3d0b Иммутабельные структуры данных предоставляют вам дешёвый способ отслеживания изменений в объектах и всё, что вам нужно для реализации `shouldComponentUpdate`. В большинстве случаев это даст вам хороший прирост в производительности. diff --git a/content/docs/reference-glossary.md b/content/docs/reference-glossary.md index 88bc7a241..a91c0acf7 100644 --- a/content/docs/reference-glossary.md +++ b/content/docs/reference-glossary.md @@ -131,7 +131,11 @@ class Welcome extends React.Component { Методы жизненного цикла — это настраиваемые функции, которые выполняются на различных этапах жизни компонента. Существуют специальные методы для первоначального рендеринга компонента в DOM ([монтирование](/docs/react-component.html#mounting)), его обновления, размонтирования и удаления. +<<<<<<< HEAD ## [Управляемые](/docs/forms.html#controlled-components) и [неуправляемые компоненты](/docs/uncontrolled-components.html) +======= +The most important difference between `state` and `props` is that `props` are passed from a parent component, but `state` is managed by the component itself. A component cannot change its `props`, but it can change its `state`. +>>>>>>> d0f2db967a38e358bd59c65e981862cdf38f3d0b В React существует два различных подхода для управления формами. diff --git a/content/docs/state-and-lifecycle.md b/content/docs/state-and-lifecycle.md index 3032033e1..26605a749 100644 --- a/content/docs/state-and-lifecycle.md +++ b/content/docs/state-and-lifecycle.md @@ -72,9 +72,13 @@ ReactDOM.render( «Состояние» очень похоже на уже знакомые нам пропсы, отличие в том, что состояние контролируется и доступно только конкретному компоненту. +<<<<<<< HEAD Мы [уже упоминали](/docs/components-and-props.html#functional-and-class-components), что классовые компоненты обладают дополнительными способностями. Внутреннее «состояние» — одна из таких способностей, которое доступно только классовым компонентам. ## Преобразование функции в класс {#converting-a-function-to-a-class} +======= +## Converting a Function to a Class {#converting-a-function-to-a-class} +>>>>>>> d0f2db967a38e358bd59c65e981862cdf38f3d0b Давайте преобразуем функциональный компонент `Clock` в классовый компонент за 5 шагов: diff --git a/content/languages.yml b/content/languages.yml index 5e0958260..844607526 100644 --- a/content/languages.yml +++ b/content/languages.yml @@ -66,15 +66,23 @@ - name: Italian translated_name: Italiano code: it - status: 0 + status: 1 - name: Japanese translated_name: 日本語 code: ja status: 2 +- name: Georgian + translated_name: ქართული + code: ka + status: 0 - name: Central Khmer translated_name: ភាសាខ្មែរ code: km status: 0 +- name: Kannada + translated_name: ಕನ್ನಡ + code: kn + status: 0 - name: Korean translated_name: 한국어 code: ko @@ -126,6 +134,7 @@ - name: Swedish translated_name: Svenska code: sv + status: 0 - name: Tamil translated_name: தமிழ் code: ta @@ -134,10 +143,14 @@ translated_name: తెలుగు code: te status: 0 +- name: Thai + translated_name: ไทย + code: th + status: 0 - name: Turkish translated_name: Türkçe code: tr - status: 1 + status: 2 - name: Ukrainian translated_name: Українська code: uk @@ -157,7 +170,7 @@ - name: Simplified Chinese translated_name: 简体中文 code: zh-hans - status: 1 + status: 2 - name: Traditional Chinese translated_name: 繁體中文 code: zh-hant diff --git a/package.json b/package.json index de8035421..bf7b03428 100644 --- a/package.json +++ b/package.json @@ -46,8 +46,8 @@ "normalize.css": "^8.0.0", "prettier": "^1.7.4", "prismjs": "^1.15.0", - "react": "16.8.3", - "react-dom": "16.8.3", + "react": "16.8.6", + "react-dom": "16.8.6", "react-helmet": "^5.2.0", "react-live": "1.8.0-0", "remarkable": "^1.7.1", diff --git a/src/site-constants.js b/src/site-constants.js index 715b332fa..9a1775b75 100644 --- a/src/site-constants.js +++ b/src/site-constants.js @@ -7,8 +7,13 @@ // NOTE: We can't just use `location.toString()` because when we are rendering // the SSR part in node.js we won't have a proper location. +<<<<<<< HEAD const urlRoot = 'https://ru.reactjs.org'; const version = '16.8.4'; +======= +const urlRoot = 'https://reactjs.org'; +const version = '16.8.6'; +>>>>>>> d0f2db967a38e358bd59c65e981862cdf38f3d0b const babelURL = 'https://unpkg.com/babel-standalone@6.26.0/babel.min.js'; export {babelURL, urlRoot, version}; diff --git a/yarn.lock b/yarn.lock index deb7190eb..ae804aad8 100644 --- a/yarn.lock +++ b/yarn.lock @@ -10220,15 +10220,15 @@ react-dev-utils@^4.2.1: strip-ansi "3.0.1" text-table "0.2.0" -react-dom@16.8.3: - version "16.8.3" - resolved "https://registry.yarnpkg.com/react-dom/-/react-dom-16.8.3.tgz#ae236029e66210783ac81999d3015dfc475b9c32" - integrity sha512-ttMem9yJL4/lpItZAQ2NTFAbV7frotHk5DZEHXUOws2rMmrsvh1Na7ThGT0dTzUIl6pqTOi5tYREfL8AEna3lA== +react-dom@16.8.6: + version "16.8.6" + resolved "https://registry.yarnpkg.com/react-dom/-/react-dom-16.8.6.tgz#71d6303f631e8b0097f56165ef608f051ff6e10f" + integrity sha512-1nL7PIq9LTL3fthPqwkvr2zY7phIPjYrT0jp4HjyEQrEROnw4dG41VVwi/wfoCneoleqrNX7iAD+pXebJZwrwA== dependencies: loose-envify "^1.1.0" object-assign "^4.1.1" prop-types "^15.6.2" - scheduler "^0.13.3" + scheduler "^0.13.6" react-error-overlay@^3.0.0: version "3.0.0" @@ -10282,15 +10282,15 @@ react-side-effect@^1.1.0: exenv "^1.2.1" shallowequal "^1.0.1" -react@16.8.3: - version "16.8.3" - resolved "https://registry.yarnpkg.com/react/-/react-16.8.3.tgz#c6f988a2ce895375de216edcfaedd6b9a76451d9" - integrity sha512-3UoSIsEq8yTJuSu0luO1QQWYbgGEILm+eJl2QN/VLDi7hL+EN18M3q3oVZwmVzzBJ3DkM7RMdRwBmZZ+b4IzSA== +react@16.8.6: + version "16.8.6" + resolved "https://registry.yarnpkg.com/react/-/react-16.8.6.tgz#ad6c3a9614fd3a4e9ef51117f54d888da01f2bbe" + integrity sha512-pC0uMkhLaHm11ZSJULfOBqV4tIZkx87ZLvbbQYunNixAAvjnC+snJCg0XQXn9VIsttVsbZP/H/ewzgsd5fxKXw== dependencies: loose-envify "^1.1.0" object-assign "^4.1.1" prop-types "^15.6.2" - scheduler "^0.13.3" + scheduler "^0.13.6" read-all-stream@^3.0.0: version "3.1.0" @@ -10964,10 +10964,10 @@ sax@>=0.6.0, sax@^1.2.4, sax@~1.2.1, sax@~1.2.4: resolved "https://registry.yarnpkg.com/sax/-/sax-1.2.4.tgz#2816234e2378bddc4e5354fab5caa895df7100d9" integrity sha512-NqVDv9TpANUjFm0N8uM5GxL36UgKi9/atZw+x7YFnQ8ckwFGKrl4xX4yWtrey3UJm5nP1kUbnYgLopqWNSRhWw== -scheduler@^0.13.3: - version "0.13.3" - resolved "https://registry.yarnpkg.com/scheduler/-/scheduler-0.13.3.tgz#bed3c5850f62ea9c716a4d781f9daeb9b2a58896" - integrity sha512-UxN5QRYWtpR1egNWzJcVLk8jlegxAugswQc984lD3kU7NuobsO37/sRfbpTdBjtnD5TBNFA2Q2oLV5+UmPSmEQ== +scheduler@^0.13.6: + version "0.13.6" + resolved "https://registry.yarnpkg.com/scheduler/-/scheduler-0.13.6.tgz#466a4ec332467b31a91b9bf74e5347072e4cd889" + integrity sha512-IWnObHt413ucAYKsD9J1QShUKkbKLQQHdxRyw73sw4FN26iWr3DY/H34xGPe4nmL1DwXyWmSWmMrA9TfQbE/XQ== dependencies: loose-envify "^1.1.0" object-assign "^4.1.1"