|
1 | | -If you are reporting a bug, please fill in below. Otherwise feel free to remove this template entirely. |
| 1 | +<!-- |
| 2 | + PLEASE READ THE FIRST SECTION :-) |
| 3 | +--> |
2 | 4 |
|
3 | | -### Can you reproduce the problem with latest npm? |
| 5 | +### Is this a bug report? |
4 | 6 |
|
5 | | -Many errors, especially related to "missing modules", are due to npm bugs. |
| 7 | +(write your answer here) |
6 | 8 |
|
7 | | -If you're using Windows, [follow these instructions to update npm](https://github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows). |
| 9 | +<!-- |
| 10 | + If you answered "Yes": |
| 11 | + |
| 12 | + Please note that your issue will be fixed much faster if you spend about |
| 13 | + half an hour preparing it, including the exact reproduction steps and a demo. |
| 14 | + |
| 15 | + If you're in a hurry or don't feel confident, it's fine to report bugs with |
| 16 | + less details, but this makes it less likely they'll get fixed soon. |
8 | 17 |
|
9 | | -If you're using OS X or Linux, run this to update npm: |
| 18 | + In either case, please fill as many fields below as you can. |
10 | 19 |
|
11 | | -``` |
12 | | -npm install -g npm@latest |
| 20 | + If you answered "No": |
13 | 21 |
|
14 | | -cd your_project_directory |
15 | | -rm -rf node_modules |
16 | | -npm install |
17 | | -``` |
| 22 | + If this is a question or a discussion, you may delete this template and write in a free form. |
| 23 | + Note that we don't provide help for webpack questions after ejecting. |
| 24 | + You can find webpack docs at https://webpack.js.org/. |
| 25 | +--> |
18 | 26 |
|
19 | | -Then try to reproduce the issue again. |
20 | 27 |
|
21 | | -Can you still reproduce it? |
| 28 | +### Can you also reproduce the problem with npm 4.x? |
22 | 29 |
|
23 | | -### Description |
| 30 | +<!-- |
| 31 | + Many errors, especially related to "missing modules", are due to npm bugs. |
| 32 | + Which version of npm are you running? You can find out by checking: |
24 | 33 |
|
25 | | -What are you reporting? |
| 34 | + npm -v |
26 | 35 |
|
27 | | -### Expected behavior |
| 36 | + If it is 5.x, please be aware that it has more than 50 known bugs, and |
| 37 | + is not guaranteed to work with Create React App. |
28 | 38 |
|
29 | | -Tell us what you think should happen. |
| 39 | + If it's not starting with 4, try to install npm 4.x: |
30 | 40 |
|
31 | | -### Actual behavior |
| 41 | + npm install -g npm@4 |
| 42 | + cd your_project_directory |
| 43 | + rm -rf node_modules |
| 44 | + npm cache clear |
| 45 | + npm install |
| 46 | +
|
| 47 | + Then try to reproduce the issue again. |
| 48 | + Can you still reproduce it? |
| 49 | +
|
| 50 | + Note: Please try this even if you are using Yarn so that we know whether it's a Yarn-only bug. |
| 51 | +--> |
| 52 | + |
| 53 | +(Write your answer here.) |
| 54 | + |
| 55 | + |
| 56 | +### Which terms did you search for in User Guide? |
| 57 | + |
| 58 | +<!-- |
| 59 | + There are a few common documented problems, such as watcher not detecting changes, or build failing. |
| 60 | + They are described in the Troubleshooting section of the User Guide: |
| 61 | +
|
| 62 | + https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md#troubleshooting |
| 63 | +
|
| 64 | + Please scan these few sections for common problems. |
| 65 | + Additionally, you can search the User Guide itself for something you're having issues with: |
| 66 | + |
| 67 | + https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.me |
| 68 | + |
| 69 | + If you didn't find the solution, please share which words you searched for. |
| 70 | + This helps us improve documentation for future readers who might encounter the same problem. |
| 71 | +--> |
| 72 | + |
| 73 | +(Write your answer here if relevant.) |
32 | 74 |
|
33 | | -Tell us what actually happens. |
34 | 75 |
|
35 | 76 | ### Environment |
36 | 77 |
|
37 | | -Run these commands in the project folder and fill in their results: |
| 78 | +<!-- |
| 79 | + Please fill in all the relevant fields by running these commands in terminal. |
| 80 | +--> |
38 | 81 |
|
39 | | -1. `npm ls react-scripts` (if you haven’t ejected): |
40 | | -2. `node -v`: |
41 | | -3. `npm -v`: |
| 82 | +1. `node -v`: |
| 83 | +2. `npm -v`: |
| 84 | +4. `yarn --version` (if you use Yarn): |
| 85 | +3. `npm ls react-scripts` (if you haven’t ejected): |
42 | 86 |
|
43 | 87 | Then, specify: |
44 | 88 |
|
45 | 89 | 1. Operating system: |
46 | | -2. Browser and version: |
| 90 | +2. Browser and version (if relevant): |
| 91 | + |
| 92 | + |
| 93 | +### Steps to Reproduce |
| 94 | + |
| 95 | +<!-- |
| 96 | + How would you describe your issue to someone who doesn’t know you or your project? |
| 97 | + Try to write a sequence of steps that anybody can repeat to see the issue. |
| 98 | +--> |
| 99 | + |
| 100 | +(Write your steps here:) |
| 101 | + |
| 102 | +1. |
| 103 | +2. |
| 104 | +3. |
| 105 | + |
| 106 | + |
| 107 | +### Expected Behavior |
| 108 | + |
| 109 | +<!-- |
| 110 | + How did you expect the tool to behave? |
| 111 | + It’s fine if you’re not sure your understanding is correct. |
| 112 | + Just write down what you thought would happen. |
| 113 | +--> |
| 114 | + |
| 115 | +(Write what you thought would happen.) |
| 116 | + |
| 117 | + |
| 118 | +### Actual Behavior |
| 119 | + |
| 120 | +<!-- |
| 121 | + Did something go wrong? |
| 122 | + Is something broken, or not behaving as you expected? |
| 123 | + Please attach screenshots if possible! They are extremely helpful for diagnosing issues. |
| 124 | +--> |
| 125 | + |
| 126 | +(Write what happened. Please add screenshots!) |
| 127 | + |
47 | 128 |
|
48 | 129 | ### Reproducible Demo |
49 | 130 |
|
50 | | -Please take the time to create a new app that reproduces the issue. |
| 131 | +<!-- |
| 132 | + If you can, please share a project that reproduces the issue. |
| 133 | + This is the single most effective way to get an issue fixed soon. |
| 134 | +
|
| 135 | + There are two ways to do it: |
| 136 | +
|
| 137 | + * Create a new app and try to reproduce the issue in it. |
| 138 | + This is useful if you roughly know where the problem is, or can’t share the real code. |
| 139 | +
|
| 140 | + * Or, copy your app and remove things until you’re left with the minimal reproducible demo. |
| 141 | + This is useful for finding the root cause. You may then optionally create a new project. |
51 | 142 |
|
52 | | -Alternatively, you could copy your app that experiences the problem and start removing things until you’re left with the minimal reproducible demo. |
| 143 | + This is a good guide to creating bug demos: https://stackoverflow.com/help/mcve |
| 144 | + Once you’re done, push the project to GitHub and paste the link to it below: |
| 145 | +--> |
53 | 146 |
|
54 | | -(Accidentally, you might get to the root of your problem during that process.) |
| 147 | +(Paste the link to an example project and exact instructions to reproduce the issue.) |
55 | 148 |
|
56 | | -Push to GitHub and paste the link here. |
| 149 | +<!-- |
| 150 | + What happens if you skip this step? |
| 151 | + |
| 152 | + We will try to help you, but in many cases it is impossible because crucial |
| 153 | + information is missing. In that case we'll tag an issue as having a low priority, |
| 154 | + and eventually close it if there is no clear direction. |
| 155 | + |
| 156 | + We still appreciate the report though, as eventually somebody else might |
| 157 | + create a reproducible example for it. |
57 | 158 |
|
58 | | -By doing this, you're helping the Create React App contributors a big time! |
59 | | -Demonstrable issues gets fixed faster. |
| 159 | + Thanks for helping us help you! |
| 160 | +--> |
0 commit comments