Skip to content
This repository has been archived by the owner on Mar 9, 2021. It is now read-only.

[Bug] Can not Create new Project on Windows 10 #299

Open
conradkirschner opened this issue Nov 6, 2019 · 8 comments
Open

[Bug] Can not Create new Project on Windows 10 #299

conradkirschner opened this issue Nov 6, 2019 · 8 comments

Comments

@conradkirschner
Copy link

Can not create new Project


What's going on?
I've installed ignite globally on Windows 10.
Then I tried to use the wizzard to create a new project


  • adding ignite-andross
  • installing boilerplate
  • using the Infinite Red boilerplate v2 (code name 'Andross')
    √ using the Infinite Red boilerplate v2 (code name 'Andross')
  • adding React Native 0.59.9 (30 seconds-ish)
    √ added React Native 0.59.9 in 34.66s
    an error occured while installing ignite-andross boilerplate.
    Error: ENOENT: no such file or directory, chdir 'C:\Users\conrad\Desktop\programming project\react-native\ignite\NewsApi' -> 'NewsApi'
    at process.chdir (internal/process/main_thread_only.js:29:13)
    at Object. (C:\Users\conrad\AppData\Roaming\npm\node_modules\ignite-cli\build\extensions\reactNative.js:114:33)
    at step (C:\Users\conrad\AppData\Roaming\npm\node_modules\ignite-cli\build\extensions\reactNative.js:32:23)
    at Object.next (C:\Users\conrad\AppData\Roaming\npm\node_modules\ignite-cli\build\extensions\reactNative.js:13:53)
    at fulfilled (C:\Users\conrad\AppData\Roaming\npm\node_modules\ignite-cli\build\extensions\reactNative.js:4:58)
    at processTicksAndRejections (internal/process/task_queues.js:93:5) {
    errno: -4058,
    code: 'ENOENT',
    syscall: 'chdir',
    path: 'C:\Users\conrad\Desktop\programming project\react-native\ignite\NewsApi',
    dest: 'NewsApi'
    }
    error installing boilerplate

Doctor output
System
platform win32
arch x64
cpu 8 cores Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
directory ignite C:\Users\conrad\Desktop\programming project\react-native\ignite

JavaScript
node 12.13.0 C:\Program Files\nodejs\node.EXE
npm 6.12.0 C:\Program Files\nodejs\npm.CMD
yarn 1.19.1 C:\Users\conrad\AppData\Roaming\npm\yarn.CMD

Ignite
ignite-cli 3.3.1 C:\Users\conrad\AppData\Roaming\npm\ignite.CMD
ignite src build C:\Users\conrad\AppData\Roaming\npm\node_modules\ignite-cli\build
generators {}

Android
java - C:\Program Files\Java\jdk-12.0.1\bin\java.EXE
android home - C:\Users\conrad\AppData\Local\Android\Sdk

@conradkirschner
Copy link
Author

conradkirschner commented Nov 6, 2019

to get it work, i had to install it NOT GLOBAL should be written into readme, or fixed (this only apears to andross)

seems that it can not finish (stuck on creation)

@egemenkayalidere
Copy link

I have the same issue. How to solve it ?

@egemenkayalidere
Copy link

I found a solution. I reinstalled homebrew, node & npm, ignite-cli, react-native-cli and it worked !

@Venipa
Copy link

Venipa commented Nov 12, 2019

I found a solution. I reinstalled homebrew, node & npm, ignite-cli, react-native-cli and it worked !

this issue is related to Windows 10, homebrew is for mac afaik so this is still unsolved for op.

im currently having the same issue on Windows 10 1903, the setup just stops afterwards
image

@egemenkayalidere
Copy link

Yes, you are right and I know the homebrew is for mac too. I suggest you guys to use this way that you reinstall node & npm, ignite-cli, react-native-cli to solve your case. Forget homebrew.

@masonlin
Copy link

masonlin commented Nov 14, 2019

I found a solution. I reinstalled homebrew, node & npm, ignite-cli, react-native-cli and it worked !

I have the same issue, and follow your suggest to uninstall all of those packages and reinstall to solve it for the ignite-bowser, but the ignite-andross still have the same error message. Thank you.

@jamonholmgren jamonholmgren transferred this issue from infinitered/ignite Nov 21, 2019
@SPopenko
Copy link

SPopenko commented Dec 2, 2019

@conradkirschner could you please share your workaround here?

@conradkirschner
Copy link
Author

conradkirschner commented Dec 4, 2019

@conradkirschner could you please share your workaround here?

Reinstalled windows then it worked (only yarn as global installation), nevertheless such a unstable boilerplate is nothing that I want to use

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants