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
-[Displaying Lint Output in the Editor](#displaying-lint-output-in-the-editor)
19
+
-[Adding Bootstrap](#adding-bootstrap)
20
20
-[Adding Flow](#adding-flow)
21
21
-[Deploying](#deploying)
22
22
-[Something Missing?](#something-missing)
@@ -88,7 +88,46 @@ Instead, it will copy all the configuration files and the transitive dependencie
88
88
89
89
You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
90
90
91
-
## How To...
91
+
## How To
92
+
93
+
### Displaying Lint Output in the Editor
94
+
95
+
>Note: this feature is available with `[email protected]` and higher.
96
+
97
+
Some editors, including Sublime Text, Atom, and Visual Studio Code, provide plugins for ESLint.
98
+
99
+
They are not required for linting. You should see the linter output right in your terminal as well as the browser console. However, if you prefer the lint results to appear right in your editor, there are some extra steps you can do.
100
+
101
+
You would need to install an ESLint plugin for your editor first.
102
+
103
+
>**A note for Atom `linter-eslint` users**
104
+
105
+
>If you are using the Atom `linter-eslint` plugin, make sure that **Use global ESLint installation** option is checked:
We recognize that this is suboptimal, but it is currently required due to the way we hide the ESLint dependency. The ESLint team is already [working on a solution to this](https://github.com/eslint/eslint/issues/3458) so this may become unnecessary in a couple of months.
130
+
92
131
93
132
### Installing a Dependency
94
133
@@ -247,9 +286,9 @@ Please be advised that this is also a custom feature of Webpack.
247
286
248
287
**It is not required for React** but many people enjoy it (and React Native uses a similar mechanism for images). However it may not be portable to some other environments, such as Node.js and Browserify. If you prefer to reference static assets in a more traditional way outside the module system, please let us know [in this issue](https://github.com/facebookincubator/create-react-app/issues/28), and we will consider support for this.
249
288
250
-
### Installing React Bootstrap
289
+
### Adding Bootstrap
251
290
252
-
You don’t have to use React Bootstrap together with React but it is a popular library for integrating Bootstrap with React apps. If you need it, you can integrate it with Create React App by following these steps:
291
+
You don’t have to use [React Bootstrap](https://react-bootstrap.github.io) together with React but it is a popular library for integrating Bootstrap with React apps. If you need it, you can integrate it with Create React App by following these steps:
253
292
254
293
**Step 1.** Install React Bootstrap and Bootstrap from NPM. React Bootstrap does not include Bootstrap CSS so this needs to be installed as well.
Now you are ready to use the imported React Bootstrap components within your component hierarchy defined in the render method. Here is an example [`App.js`](https://gist.githubusercontent.com/gaearon/85d8c067f6af1e56277c82d19fd4da7b/raw/6158dd991b67284e9fc8d70b9d973efe87659d72/App.js) redone using React Bootstrap.
275
314
276
-
### Displaying Lint Output in the Editor
277
-
278
-
>Note: this feature is available with `[email protected]` and higher.
279
-
280
-
Some editors, including Sublime Text, Atom, and Visual Studio Code, provide plugins for ESLint.
281
-
282
-
They are not required for linting. You should see the linter output right in your terminal as well as the browser console. However, if you prefer the lint results to appear right in your editor, there are some extra steps you can do.
283
-
284
-
You would need to install an ESLint plugin for your editor first.
285
-
286
-
>**A note for Atom `linter-eslint` users**
287
-
288
-
>If you are using the Atom `linter-eslint` plugin, make sure that **Use global ESLint installation** option is checked:
We recognize that this is suboptimal, but it is currently required due to the way we hide the ESLint dependency. The ESLint team is already [working on a solution to this](https://github.com/eslint/eslint/issues/3458) so this may become unnecessary in a couple of months.
313
-
314
315
### Adding Flow
315
316
316
317
Flow typing is currently [not supported out of the box](https://github.com/facebookincubator/create-react-app/issues/72) with the default `.flowconfig` generated by Flow. If you run it, you might get errors like this:
0 commit comments