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
Copy file name to clipboardExpand all lines: packages/react-scripts/template/README.md
-59Lines changed: 0 additions & 59 deletions
Original file line number
Diff line number
Diff line change
@@ -178,48 +178,7 @@ Some editors, including Sublime Text, Atom, and Visual Studio Code, provide plug
178
178
179
179
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.
180
180
181
-
<<<<<<< HEAD
182
181
You would need to install an TSLint plugin for your editor first.
183
-
=======
184
-
You would need to install an ESLint plugin for your editor first.
185
-
186
-
>**A note for Atom `linter-eslint` users**
187
-
188
-
>If you are using the Atom `linter-eslint` plugin, make sure that **Use global ESLint installation** option is checked:
>VS Code ESLint plugin automatically detects Create React App's configuration file. So you do not need to create `eslintrc.json` at the root directory, except when you want to add your own rules. In that case, you should include CRA's config by adding this line:
196
-
197
-
>```js
198
-
{
199
-
// ...
200
-
"extends":"react-app"
201
-
}
202
-
```
203
-
204
-
Then add this block to the `package.json` file of your project:
205
-
206
-
```js
207
-
{
208
-
// ...
209
-
"eslintConfig": {
210
-
"extends":"react-app"
211
-
}
212
-
}
213
-
```
214
-
215
-
Finally, you will need to install some packages *globally*:
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.
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.
498
457
499
-
## Adding Flow
500
-
501
-
Flow is a static type checker that helps you write code with fewer bugs. Check out this [introduction to using static types in JavaScript](https://medium.com/@preethikasireddy/why-use-static-types-in-javascript-part-1-8382da1e0adb) if you are new to this concept.
502
-
503
-
Recent versions of [Flow](http://flowtype.org/) work with Create React App projects out of the box.
504
-
505
-
To add Flow to a Create React App project, follow these steps:
506
-
507
-
1. Run `npm install --save-dev flow-bin`.
508
-
2. Add `"flow": "flow"` to the `scripts` section of your `package.json`.
509
-
3. Add `// @flow` to any files you want to type check (for example, to `src/App.js`).
510
-
511
-
Now you can run `npm run flow` to check the files for type errors.
512
-
You can optionally use an IDE like [Nuclide](https://nuclide.io/docs/languages/flow/) for a better integrated experience.
513
-
In the future we plan to integrate it into Create React App even more closely.
514
-
515
-
To learn more about Flow, check out [its documentation](https://flowtype.org/).
516
-
517
458
## Adding Custom Environment Variables
518
459
519
460
>Note: this feature is available with `[email protected]` and higher.
0 commit comments