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
+4-29
Original file line number
Diff line number
Diff line change
@@ -158,7 +158,7 @@ See the section about [deployment](#deployment) for more information.
158
158
159
159
If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project.
160
160
161
-
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
161
+
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, TSLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
162
162
163
163
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.
164
164
@@ -170,36 +170,11 @@ To configure the syntax highlighting in your favorite text editor, head to the [
170
170
171
171
>Note: this feature is available with `react-scripts@0.2.0` and higher.
172
172
173
-
Some editors, including Sublime Text, Atom, and Visual Studio Code, provide plugins for ESLint.
173
+
Some editors, including Sublime Text, Atom, and Visual Studio Code, provide plugins for TSLint.
174
174
175
175
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.
176
176
177
-
You would need to install an ESLint plugin for your editor first.
178
-
179
-
>**A note for Atom `linter-eslint` users**
180
-
181
-
>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.
177
+
You would need to install an TSLint plugin for your editor first.
203
178
204
179
## Changing the Page `<title>`
205
180
@@ -448,7 +423,7 @@ const $ = window.$;
448
423
449
424
This makes it obvious you are using a global variable intentionally rather than because of a typo.
450
425
451
-
Alternatively, you can force the linter to ignore any line by adding `// eslint-disable-line` after it.
426
+
Alternatively, you can force the linter to ignore any line by adding `// tslint:disable-line` after it.
0 commit comments