You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -44,13 +41,11 @@ This library is an evolution of [`code-split-component`](). Unlike `code-split-c
44
41
45
42
## Examples
46
43
47
-
### End to End Examples
48
-
49
44
The below examples show off a full workflow of using the `createAsyncComponent` and `withAsyncComponents` helpers.
50
45
51
-
In all of our examples below we are going to be making use of the `System.import` API supported by Webpack v2 to do asynchronous resolution of our Components and create code split points.
46
+
In some of the examples below we are going to be making use of the `System.import` API supported by Webpack v2 which provides us with code splitting on our asynchronous components.
52
47
53
-
####Browser Only Application
48
+
### Browser Only Application
54
49
55
50
This is how you would use `react-async-component` in a "browser only" React application.
56
51
@@ -136,7 +131,7 @@ export default Root;
136
131
137
132
You have a lot more power than is shown here. Be sure to check out the [`API`](#api) and [`Examples`](#examples) sections for more.
138
133
139
-
####Server Side Rendering Application
134
+
### Server Side Rendering Application
140
135
141
136
In a "server side rendering" React application you can use the async components in the same manner as described above, but you need to make some adjustments to the way that you render the application on the server.
Note: `System.import` is considered deprecated and will be replaced with `import`, but for now they can be used interchangeably (you may need a Babel plugin for the `import` syntax).
0 commit comments