-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to Run on Windows #420
Comments
Hi @ahoadshieldpay, Thanks for this report. Which version of Windows are you running? |
Version: Windows 10 pro |
Getting exactly same issue in Win 7 as well, using cmd terminal. |
Hello and sorry to intrude in this post. Just want to say that I was having the same issue on Windows 10. However, I cloned the Thanks @kevinold. That was a quick response 👍 |
@frogcatcher the draft PR is displayed within this thread above, here is the PR link for your convenience: #421 |
I've also just tried cloning the pull request and things are getting further, but on running yarn start or yarn dev I am now getting a compile error:
|
@frogcatcher the pull request is code that has been sent to a specific branch, that's where it's tested and prepare before merging to the main one. The branch it was sent to is that one that I mentioned before. You can look for the different branches while being on the @ahoadshieldpay that might be happening because if you check the pull request, there are new dependencies added in the package.json. |
@LucasL94 we appreciate your efforts in helping out the community. 🙏 |
@LucasL94 still no luck, but thanks for the help. I tried again from the beginning - deleted it all and cloned again, checkout to the pull request and ran through the steps again including yarn install. Still getting compile error: |
Hi @ahoadshieldpay, What version of Node are you running? In the VS Code Terminal type These updates are set to work against Node version 12.x |
v14.3.0 |
@ahoadshieldpay Yes, that is the issue you are seeing now. We are using Node version 12, so you will need to downgrade in order to use this application. |
I have downgraded, now on v12.18.0 Went through all the steps again but still getting the same error. |
I gave up and removed everything and did a new git. And got the same errors. Also, been following the threads. I continue to get stuck on this error when I enter the command yarn start or yarn dev.$ yarn db:seed:dev
|
You do not need to modify any of the code on the Follow these steps to use the
|
@ahoadshieldpay Reclone the project into a new directory and verify in the terminal in VS Code that it is using Node 12.18 (via |
Thank you kevinold and everyone! Mine is working now. :) |
I am experiencing the same behavior as @ahoadshieldpay where I am getting a Failed to Compile error on execution. Full error below. Node: v12.18.0
Error received:
|
@kpmck Thanks for this report. Investigating further. cc @ahoadshieldpay |
@ahoadshieldpay @kpmck I've confirmed I'm able to reproduce this "Failed to compile" error locally and am investigating further. |
Hey @kevinold . Could you try with some of the following? A. Deleting B. Running C. Adding I think that some of those might fix the issue. Deleting the yarn.lock without knowing what the actual problem is might be a bad practice though |
* install ncp and cross-env; update npm scripts * downgrade react scripts to 3.40 for windows; move tsnode config to file facebook/create-react-app#8707 (comment) * update circle config to run tests on windows * update windows run to use cypress orb * update windows executor * require setup for windows build * downgrade babel-loader for react-scripts 3.4.0 * setup linux and windows workflows * update windows workflow to install google chrome and run test in chrome * update windows to run against electron * wait for notifications * update with additional wait for notifications * add additional wait for notifications * add additional notifications wait * add additional assertion to make sure the list has been updated * update to fix flake * fix length counts for flake * update to fix count and waits for flake * add assertion to retry for correct count * ensure the like registers * name jobs * cypress info on Windows * disable install of google chrome on windows * wait on comment to be posted to fix flake * resolve babel/compat-data to v7.9.0 to fix failed to compile error #420 (comment) Co-authored-by: Gleb Bahmutov <gleb.bahmutov@gmail.com>
@kevinold Thank you for the quick fix, it's now working |
* install ncp and cross-env; update npm scripts * downgrade react scripts to 3.40 for windows; move tsnode config to file facebook/create-react-app#8707 (comment) * update circle config to run tests on windows * update windows run to use cypress orb * update windows executor * require setup for windows build * downgrade babel-loader for react-scripts 3.4.0 * setup linux and windows workflows * update windows workflow to install google chrome and run test in chrome * update windows to run against electron * wait for notifications * update with additional wait for notifications * add additional wait for notifications * add additional notifications wait * add additional assertion to make sure the list has been updated * update to fix flake * fix length counts for flake * update to fix count and waits for flake * add assertion to retry for correct count * ensure the like registers * name jobs * cypress info on Windows * disable install of google chrome on windows * wait on comment to be posted to fix flake * resolve babel/compat-data to v7.9.0 to fix failed to compile error cypress-io#420 (comment) Co-authored-by: Gleb Bahmutov <gleb.bahmutov@gmail.com>
Cloned the repository
ran yarn install
On running yarn start i got the below error:
$ cp data/database-seed.json data/database.json 'cp' is not recognized as an internal or external command, operable program or batch file.
Changed the cp commands to copy so they would work on windows.
Then got the below error:
$ copy data/database-seed.json data/database.json data\database-seed.json The file cannot be copied onto itself. 0 file(s) copied.
Changed the / in package.json to \
Then got the below error:
NODE_ENV=development concurrently yarn:start:react yarn:start:api 'NODE_ENV' is not recognized as an internal or external command, operable program or batch file.
Added SET before NODE_ENV
No errors on running yarn start this time but also appears that nothing has started
Run yarn cypress:open and try running a test
Get errors due to app not starting
The text was updated successfully, but these errors were encountered: