|
| 1 | +<!-- |
| 2 | + PLEASE READ THE FIRST SECTION :-) |
| 3 | +--> |
| 4 | + |
| 5 | +### Is this a bug report? |
| 6 | + |
| 7 | +(write your answer here) |
| 8 | + |
| 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. |
| 17 | +
|
| 18 | + In either case, please fill as many fields below as you can. |
| 19 | +
|
| 20 | + If you answered "No": |
| 21 | +
|
| 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 | +--> |
| 26 | + |
| 27 | +### Did you try recovering your dependencies? |
| 28 | + |
| 29 | +<!-- |
| 30 | + Your module tree might be corrupted, and that might be causing the issues. |
| 31 | + Let's try to recover it. First, delete these files and folders in your project: |
| 32 | +
|
| 33 | + * node_modules |
| 34 | + * package-lock.json |
| 35 | + * yarn.lock |
| 36 | +
|
| 37 | + Then you need to decide which package manager you prefer to use. |
| 38 | + We support both npm (https://npmjs.com) and yarn (http://yarnpkg.com/). |
| 39 | + However, **they can't be used together in one project** so you need to pick one. |
| 40 | + |
| 41 | + If you decided to use npm, run this in your project directory: |
| 42 | +
|
| 43 | + npm install -g npm@latest |
| 44 | + npm install |
| 45 | +
|
| 46 | + This should fix your project. |
| 47 | + |
| 48 | + If you decided to use yarn, update it first (https://yarnpkg.com/en/docs/install). |
| 49 | + Then run in your project directory: |
| 50 | +
|
| 51 | + yarn |
| 52 | +
|
| 53 | + This should fix your project. |
| 54 | +
|
| 55 | + Importantly, **if you decided to use yarn, you should never run `npm install` in the project**. |
| 56 | + For example, yarn users should run `yarn add <library>` instead of `npm install <library>`. |
| 57 | + Otherwise your project will break again. |
| 58 | +
|
| 59 | + Have you done all these steps and still see the issue? |
| 60 | + Please paste the output of `npm --version` and/or `yarn --version` to confirm. |
| 61 | +--> |
| 62 | + |
| 63 | +(Write your answer here.) |
| 64 | + |
| 65 | +### Which terms did you search for in User Guide? |
| 66 | + |
| 67 | +<!-- |
| 68 | + There are a few common documented problems, such as watcher not detecting changes, or build failing. |
| 69 | + They are described in the Troubleshooting section of the User Guide: |
| 70 | +
|
| 71 | + https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md#troubleshooting |
| 72 | +
|
| 73 | + Please scan these few sections for common problems. |
| 74 | + Additionally, you can search the User Guide itself for something you're having issues with: |
| 75 | + |
| 76 | + https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md |
| 77 | + |
| 78 | + If you didn't find the solution, please share which words you searched for. |
| 79 | + This helps us improve documentation for future readers who might encounter the same problem. |
| 80 | +--> |
| 81 | + |
| 82 | +(Write your answer here if relevant.) |
| 83 | + |
| 84 | + |
| 85 | +### Environment |
| 86 | + |
| 87 | +<!-- |
| 88 | + To help identify if a problem is specific to a platform, browser, or module version, information about your environment is required. |
| 89 | + This enables the maintainers quickly reproduce the issue and give feedback. |
| 90 | +
|
| 91 | + Run the following command in your React app's folder in terminal. |
| 92 | + Note: The result is copied to your clipboard directly. |
| 93 | +
|
| 94 | + `npx create-react-app --info` |
| 95 | +
|
| 96 | + Paste the output of the command in the section below. |
| 97 | +--> |
| 98 | + |
| 99 | +(paste the output of the command here) |
| 100 | + |
| 101 | +### Steps to Reproduce |
| 102 | + |
| 103 | +<!-- |
| 104 | + How would you describe your issue to someone who doesn’t know you or your project? |
| 105 | + Try to write a sequence of steps that anybody can repeat to see the issue. |
| 106 | +--> |
| 107 | + |
| 108 | +(Write your steps here:) |
| 109 | + |
| 110 | +1. |
| 111 | +2. |
| 112 | +3. |
| 113 | + |
| 114 | + |
| 115 | +### Expected Behavior |
| 116 | + |
| 117 | +<!-- |
| 118 | + How did you expect the tool to behave? |
| 119 | + It’s fine if you’re not sure your understanding is correct. |
| 120 | + Just write down what you thought would happen. |
| 121 | +--> |
| 122 | + |
| 123 | +(Write what you thought would happen.) |
| 124 | + |
| 125 | + |
| 126 | +### Actual Behavior |
| 127 | + |
| 128 | +<!-- |
| 129 | + Did something go wrong? |
| 130 | + Is something broken, or not behaving as you expected? |
| 131 | + Please attach screenshots if possible! They are extremely helpful for diagnosing issues. |
| 132 | +--> |
| 133 | + |
| 134 | +(Write what happened. Please add screenshots!) |
| 135 | + |
| 136 | + |
| 137 | +### Reproducible Demo |
| 138 | + |
| 139 | +<!-- |
| 140 | + If you can, please share a project that reproduces the issue. |
| 141 | + This is the single most effective way to get an issue fixed soon. |
| 142 | +
|
| 143 | + There are two ways to do it: |
| 144 | +
|
| 145 | + * Create a new app and try to reproduce the issue in it. |
| 146 | + This is useful if you roughly know where the problem is, or can’t share the real code. |
| 147 | +
|
| 148 | + * Or, copy your app and remove things until you’re left with the minimal reproducible demo. |
| 149 | + This is useful for finding the root cause. You may then optionally create a new project. |
| 150 | +
|
| 151 | + This is a good guide to creating bug demos: https://stackoverflow.com/help/mcve |
| 152 | + Once you’re done, push the project to GitHub and paste the link to it below: |
| 153 | +--> |
| 154 | + |
| 155 | +(Paste the link to an example project and exact instructions to reproduce the issue.) |
| 156 | + |
| 157 | +<!-- |
| 158 | + What happens if you skip this step? |
| 159 | + |
| 160 | + We will try to help you, but in many cases it is impossible because crucial |
| 161 | + information is missing. In that case we'll tag an issue as having a low priority, |
| 162 | + and eventually close it if there is no clear direction. |
| 163 | + |
| 164 | + We still appreciate the report though, as eventually somebody else might |
| 165 | + create a reproducible example for it. |
| 166 | +
|
| 167 | + Thanks for helping us help you! |
| 168 | +--> |
0 commit comments