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: template/README.md
+18-7Lines changed: 18 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -38,6 +38,10 @@ You need to **put any JS and CSS files inside `src`**, or Webpack won’t see th
38
38
You can, however, create more top-level directories.
39
39
They will not be included in the production build so you can use them for things like documentation.
40
40
41
+
>**Known Issue:**
42
+
>
43
+
>You may encounter an issue where changing a file inside `src` doesn’t trigger a recompilation. Most likely this happens because the path in your filesystem differs in its casing from the path you imported. For example, if a file is called `App.js` but you are importing `app.js`, the watcher might not recognize changes to it. We are [considering](https://github.com/facebookincubator/create-react-app/issues/240) enforcing some checks to prevent this. If this doesn’t help, check out the page on [troubleshooting watching](https://webpack.github.io/docs/troubleshooting.html#watching).
44
+
41
45
## Available Scripts
42
46
43
47
In the project directory, you can run:
@@ -203,7 +207,7 @@ Here is an example:
203
207
importReactfrom'react';
204
208
importlogofrom'./logo.png'; // Tell Webpack this JS file uses this image
@@ -231,7 +235,12 @@ Please be advised that this is also a custom feature of Webpack.
231
235
232
236
>Note: this feature is available with `react-scripts@0.2.0` and higher.
233
237
234
-
Some editors, including Sublime Text and Atom, provide plugins for ESLint. You would need to install such a plugin first. Once you install and enable an ESLint plugin for your editor, make sure `package.json` of your project ends with this block:
238
+
Some editors, including Sublime Text, Atom, and Visual Studio Code, provide plugins for ESLint.
239
+
240
+
They are not required for linting. You should still 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.
241
+
242
+
You would need to install an ESLint plugin for your editor first.
243
+
Then make sure `package.json` of your project ends with this block:
235
244
236
245
```js
237
246
{
@@ -242,14 +251,16 @@ Some editors, including Sublime Text and Atom, provide plugins for ESLint. You w
242
251
}
243
252
```
244
253
245
-
Projects generated with `react-scripts@0.2.0` and higher should already have it.
254
+
Projects generated with `react-scripts@0.2.0` and higher should already have it.
255
+
If you don’t need ESLint integration with your editor, you can safely delete those three lines from your `package.json`.
246
256
247
-
There are two limitations:
257
+
Finally, you will need to install some packages *globally*:
248
258
249
-
* This only works with npm >= 3 because of [an ESLint issue](https://github.com/eslint/eslint/issues/3458).
250
-
* You can’t delete these lines. We don’t like configuration as much as you do, and [are looking for better solutions](https://github.com/facebookincubator/create-react-app/issues/215).
If you don’t need ESLint integration with your editor, you can safely delete those three lines from your `package.json`.
263
+
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.
0 commit comments