We recommend using Yarn or npm for managing front-end dependencies. If you're new to package managers, the Yarn documentation is a good place to get started.
To install React with Yarn, run:
-yarn add react@15.5.0 react-dom@15.5.0
+yarn add react@^15.5.0 react-dom@^15.5.0
To install React with npm, run:
-npm install --save react@15.5.0 react-dom@15.5.0
+npm install --save react@^15.5.0 react-dom@^15.5.0
We recommend using a bundler like webpack or Browserify so you can write modular code and bundle it together into small packages to optimize load time.
diff --git a/blog/index.html b/blog/index.html
index 6365f802cf..cc3a91b70c 100644
--- a/blog/index.html
+++ b/blog/index.html
@@ -270,10 +270,10 @@
We recommend using Yarn or npm for managing front-end dependencies. If you're new to package managers, the Yarn documentation is a good place to get started.
To install React with Yarn, run:
-yarn add react@15.5.0 react-dom@15.5.0
+yarn add react@^15.5.0 react-dom@^15.5.0
To install React with npm, run:
-npm install --save react@15.5.0 react-dom@15.5.0
+npm install --save react@^15.5.0 react-dom@^15.5.0
We recommend using a bundler like webpack or Browserify so you can write modular code and bundle it together into small packages to optimize load time.
diff --git a/contributing/codebase-overview.html b/contributing/codebase-overview.html
index 59c9ed375f..2d2528688c 100644
--- a/contributing/codebase-overview.html
+++ b/contributing/codebase-overview.html
@@ -130,7 +130,6 @@
src is the source code of React. If your change is related to the code, src is where you'll spend most of your time.docs is the React documentation website. When you change APIs, make sure to update the relevant Markdown files.examples contains a few small React demos with different build setups.packages contains metadata (such as package.json) for all packages in the React repository. Nevertheless, their source code is still located inside src.build is the build output of React. It is not in the repository but it will appear in your React clone after you build it for the first time.
diff --git a/contributing/implementation-notes.html b/contributing/implementation-notes.html
index c5ff83b39e..07f100da43 100644
--- a/contributing/implementation-notes.html
+++ b/contributing/implementation-notes.html
@@ -78,6 +78,8 @@
It is very technical and assumes a strong understanding of React public API as well as how it's divided into core, renderers, and the reconciler. If you're not very familiar with the React codebase, read the codebase overview first.
+It also assumes an understanding of the differences between React components, their instances, and elements.
+
The stack reconciler is powering all the React production code today. It is located in src/renderers/shared/stack/reconciler and is used by both React DOM and React Native.
Video: Building React from Scratch
diff --git a/docs/create-fragment.html b/docs/create-fragment.html
index a7c9ef5fc3..629f056c7b 100644
--- a/docs/create-fragment.html
+++ b/docs/create-fragment.html
@@ -124,7 +124,7 @@
The keys of the passed object (that is, left and right) are used as keys for the entire set of children, and the order of the object's keys is used to determine the order of the rendered children. With this change, the two sets of children will be properly reordered in the DOM without unmounting.
-The return value of createFragment should be treated as an opaque object; you can use the React.Children helpers to loop through a fragment but should not access it directly. Note also that we're relying on the JavaScript engine preserving object enumeration order here, which is not guaranteed by the spec but is implemented by all major browsers and VMs for objects with non-numeric keys.
+The return value of createFragment should be treated as an opaque object; you can use the React.Children helpers to loop through a fragment but should not access it directly. Note also that we're relying on the JavaScript engine preserving object enumeration order here, which is not guaranteed by the spec but is implemented by all major browsers and VMs for objects with non-numeric keys.
diff --git a/docs/lifting-state-up.html b/docs/lifting-state-up.html
index 9b68362fad..fe25d4ce25 100644
--- a/docs/lifting-state-up.html
+++ b/docs/lifting-state-up.html
@@ -333,7 +333,7 @@
- React calls the function specified as
onChange on the DOM <input>. In our case, this is the handleChange method in TemperatureInput component.
- The
handleChange method in the TemperatureInput component calls this.props.onTemperatureChange() with the new desired value. Its props, including onTemperatureChange, were provided by its parent component, the Calculator.
-- When it previously rendered, the
Calculator has specified that onTemperatureChange of the Celsius TemperatureInput is the Calculator's handleCelsiusChange method, and onTemperatureChange of the Fahrenheit TemperatureInput is the Calculator's handleFahrehnheitChange method. So either of these two Calculator methods gets called depending on which input we edited.
+- When it previously rendered, the
Calculator has specified that onTemperatureChange of the Celsius TemperatureInput is the Calculator's handleCelsiusChange method, and onTemperatureChange of the Fahrenheit TemperatureInput is the Calculator's handleFahrenheitChange method. So either of these two Calculator methods gets called depending on which input we edited.
- Inside these methods, the
Calculator component asks React to re-render itself by calling this.setState() with the new input value and the current scale of the input we just edited.
- React calls the
Calculator component's render method to learn what the UI should look like. The values of both inputs are recomputed based on the current temperature and the active scale. The temperature conversion is performed here.
- React calls the
render methods of the individual TemperatureInput components with their new props specified by the Calculator. It learns what their UI should look like.
diff --git a/feed.xml b/feed.xml
index 19936a7933..338157564a 100644
--- a/feed.xml
+++ b/feed.xml
@@ -152,10 +152,10 @@
<p>We recommend using <a href="https://yarnpkg.com/">Yarn</a> or <a href="https://www.npmjs.com/">npm</a> for managing front-end dependencies. If you're new to package managers, the <a href="https://yarnpkg.com/en/docs/getting-started">Yarn documentation</a> is a good place to get started.</p>
<p>To install React with Yarn, run:</p>
-<div class="highlight"><pre><code class="language-bash" data-lang="bash">yarn add react@15.5.0 react-dom@15.5.0
+<div class="highlight"><pre><code class="language-bash" data-lang="bash">yarn add react@^15.5.0 react-dom@^15.5.0
</code></pre></div>
<p>To install React with npm, run:</p>
-<div class="highlight"><pre><code class="language-bash" data-lang="bash">npm install --save react@15.5.0 react-dom@15.5.0
+<div class="highlight"><pre><code class="language-bash" data-lang="bash">npm install --save react@^15.5.0 react-dom@^15.5.0
</code></pre></div>
<p>We recommend using a bundler like <a href="https://webpack.js.org/">webpack</a> or <a href="http://browserify.org/">Browserify</a> so you can write modular code and bundle it together into small packages to optimize load time.</p>