Storai
July 23, 2022, 6:25am
1
Hi Community!
Recently i have started learning React while creating my first project terminal got stuck here kindly guide if i am doing any thing wrong here.
thanks in advance
after the environment is set up, open the file from the top left and click “open file” or “open folder” option
Does it always hang at the same spot in the installation? Are there never any errors?
Not sure if this is related maybe?
opened 11:14PM - 10 Jan 21 UTC
stale
needs triage
issue: bug report
<!--
Please note that your issue will be fixed much faster if you spend abo… ut
half an hour preparing it, including the exact reproduction steps and a demo.
If you're in a hurry or don't feel confident, it's fine to report bugs with
less details, but this makes it less likely they'll get fixed soon.
In either case, please use this template and fill in as many fields below as you can.
Note that we don't provide help for webpack questions after ejecting.
You can find webpack docs at https://webpack.js.org/.
-->
### Describe the bug
When using ```npx create-react-app``` on Windows in User Documents directory, the command gets stuck forever without any error output.
### Did you try recovering your dependencies?
No.
<!--
Your module tree might be corrupted, and that might be causing the issues.
Let's try to recover it. First, delete these files and folders in your project:
* node_modules
* package-lock.json
* yarn.lock
Then you need to decide which package manager you prefer to use.
We support both npm (https://npmjs.com) and yarn (http://yarnpkg.com/).
However, **they can't be used together in one project** so you need to pick one.
If you decided to use npm, run this in your project directory:
npm install -g npm@latest
npm install
This should fix your project.
If you decided to use yarn, update it first (https://yarnpkg.com/en/docs/install).
Then run in your project directory:
yarn
This should fix your project.
Importantly, **if you decided to use yarn, you should never run `npm install` in the project**.
For example, yarn users should run `yarn add <library>` instead of `npm install <library>`.
Otherwise your project will break again.
Have you done all these steps and still see the issue?
Please paste the output of `npm --version` and/or `yarn --version` to confirm.
-->
### Which terms did you search for in User Guide?
Windows 10
<!--
There are a few common documented problems, such as watcher not detecting changes, or build failing.
They are described in the Troubleshooting section of the User Guide:
https://facebook.github.io/create-react-app/docs/troubleshooting
Please scan these few sections for common problems.
Additionally, you can search the User Guide itself for something you're having issues with:
https://facebook.github.io/create-react-app/
If you didn't find the solution, please share which words you searched for.
This helps us improve documentation for future readers who might encounter the same problem.
-->
### Environment
<!--
To help identify if a problem is specific to a platform, browser, or module version, information about your environment is required.
This enables the maintainers quickly reproduce the issue and give feedback.
Run the following command in your React app's folder in terminal.
Note: The result is copied to your clipboard directly.
`npx create-react-app --info`
Paste the output of the command in the section below.
-->
```
PS C:\Users\xxx\Documents> npx create-react-app --info
Environment Info:
current version of create-react-app: 4.0.1
running from C:\Users\xxx\AppData\Roaming\npm\node_modules\create-react-app
System:
OS: Windows 10 10.0.19042
CPU: (24) x64 AMD Ryzen 9 3900X 12-Core Processor
Binaries:
Node: 14.15.4 - C:\nodejs\node.EXE
Yarn: Not Found
npm: 6.14.11 - C:\nodejs\npm.CMD
Browsers:
Chrome: 87.0.4280.141
Edge: Spartan (44.19041.423.0), Chromium (87.0.664.75)
Internet Explorer: 11.0.19041.1
npmPackages:
react: Not Found
react-dom: Not Found
react-scripts: Not Found
npmGlobalPackages:
create-react-app: Not Found
PS C:\Users\xxx\Documents>
```
Additionally, system runs default Windows 10 virus protection without any third party security software.
"Controlled folder access" is turned on. (Might be relevant)

### Steps to reproduce
<!--
How would you describe your issue to someone who doesn’t know you or your project?
Try to write a sequence of steps that anybody can repeat to see the issue.
-->
1. Install nodejs with node *.msi 64bit installer for Windows 10.
2. Open PowerShell in current user's Documents folder
3. Try create-react-app following the User Guide
4. Observe that:
```
PS C:\Users\xxx\Documents> mkdir abc
mkdir : Could not find file 'abc'.
At line:1 char:1
+ mkdir abc
+ ~~~~~~~~~
+ CategoryInfo : WriteError: (C:\Users\xxx\Documents\abc:String) [New-Item], FileNotFoundException
+ FullyQualifiedErrorId : CreateDirectoryIOError,Microsoft.PowerShell.Commands.NewItemCommand
PS C:\Users\xxx\Documents> npx create-react-app abcdefg
(Program hangs here forever, without error output.)
```
### Expected behavior
<!--
How did you expect the tool to behave?
It’s fine if you’re not sure your understanding is correct.
Just write down what you thought would happen.
-->
1. For the ```create-react-app``` itself, since this is possibly a permission or special security protection issue, it's OK that the creation fails, but I expect some error output similar to what ```mkdir``` does in this case.
2. For User Guide, a special reminder may be added for Windows 10 user to avoid system protected folders, if (1) cannot be fixed easily, or the OS error codes are difficult to understand for average users.
### Actual behavior
Program hangs forever without error output explaining if any underlying OS command or API failed.
<!--
Did something go wrong?
Is something broken, or not behaving as you expected?
Please attach screenshots if possible! They are extremely helpful for diagnosing issues.
-->
(Write what happened. Please add screenshots!)
### Reproducible demo
No, I cannot produce a demo since I cannot produce the project folder.
<!--
If you can, please share a project that reproduces the issue.
This is the single most effective way to get an issue fixed soon.
There are two ways to do it:
* Create a new app and try to reproduce the issue in it.
This is useful if you roughly know where the problem is, or can’t share the real code.
* Or, copy your app and remove things until you’re left with the minimal reproducible demo.
This is useful for finding the root cause. You may then optionally create a new project.
This is a good guide to creating bug demos: https://stackoverflow.com/help/mcve
Once you’re done, push the project to GitHub and paste the link to it below:
-->
(Paste the link to an example project and exact instructions to reproduce the issue.)
<!--
What happens if you skip this step?
We will try to help you, but in many cases it is impossible because crucial
information is missing. In that case we'll tag an issue as having a low priority,
and eventually close it if there is no clear direction.
We still appreciate the report though, as eventually somebody else might
create a reproducible example for it.
Thanks for helping us help you!
-->
### References
https://github.com/PowerShell/PowerShell/issues/8857
Maybe try a different path for the installation.
You can also try using Vite instead.
Storai
July 24, 2022, 6:27am
4
yes, it goes stuck here and gives a timeout error.
I think your server is trying to pull data from source but you created two folders. It might be confusing the server? try npx create-react-app myfirstapp without creating your own folder? “myfirstapp” should be the folder you need.
system
Closed
January 23, 2023, 9:49pm
6
This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.