Ignite: Ignite requires yarn even if yarn is installed correctly

[BetaConnector]

Hey There... I have installed yarn - yarn - v shows me:
F:>yarn -v
yarn install v0.23.2
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.12s.

I am trying to create a new App with ignite but it shows me the following error:
F:>ignite new TestApp
Ignite requires yarn >=0.21.0 to be installed.

See https://yarnpkg.com/en/docs/install on how to upgrade for your OS.

What is going wrong? Hope you can help me :)

Thanks in advance - Alex

[andrei-livadariu]

This has been giving me some trouble today, and I think I narrowed down the issue to this line of code.

I ran which yarn on my computer and got C:\Program Files (x86)\Yarn\bin\yarn.CMD. Note the spaces in the path. Ignite is essentially running the command C:\Program Files (x86)\Yarn\bin\yarn.CMD --version which fails, because it should be "C:\Program Files (x86)\Yarn\bin\yarn.CMD" --version instead.

I changed the code locally to test this out, and this line seems to work:
var result = shell.exec('"' + resolvedPath + '" ' + versionCommand, { silent: true })

[BetaConnector]

Works fine - thanks alot :)

[mwarger]

@andrei-livadariu - Where did you change that line of code? I'm bit by this bug as well.

Edit: Nevermind, I was able to find it. Line 83 of ~\AppData\Roaming\npm\node_modules\ignite-cli\src\cli\enforceGlobalDependency.js

[Slapbox]

Does not resolve the issue for me unfortunately.

Edit: I lied, it works. Somehow my changes to enforceGlobalDependency.js were not saved.

[GantMan]

@andrei-livadariu - do you want to do a PR?

[andrei-livadariu]

I wouldn't go that far :) The solution I used is just a quick hack which hasn't been tested on Linux, Mac, or any other Windows configuration. I think I would rather let someone more experienced take care of this.

[yusufola]

works for me ... @andrei-livadariu thanks a lot

[jamonholmgren]

@andrei-livadariu Oops, that's my change. :/ I'll try to get this fixed soon.

[jamonholmgren]

Actually, I'm going to ask @kevinvangelder, our resident Windows expert, to tackle this.

[skellock]

The react-native packager uses shell-quote for this.

[harry-g]

An easy workaround is to install yarn (.msi) to a dir w/o spaces, e.g.
c:\Tools\yarn works fine for me.
Still this issue might confuse/discourage new users under Windows.
Would be great if you fix it!

[GantMan]

We have a PR, would love to help someone test it! Or @kevinvangelder - can you verify your PR works? Should only take seconds.

[harry-g]

PR verified OK under Windows 10!
Details see PR 1010

[marsonmao]

Is this fixed in 2.0.0-beta.9?
I installed ignite by 'npm install -g ignite-cli', installed yarn by 'choco install yarn', all done in 30 mins from now and still having this issue.
And my yarn is installed in that x86 folder too.

[marsonmao]

Alright, seems not fixed yet, since issue closed 16 days ago and 2.0.0-beta.9 was released 26 days ago.

[jamonholmgren]

We're getting closer to releasing beta.10, but since it's the precursor to 2.0.0 we are trying to include more things. Soon!

[alicelimacd]

hi, i m also hitting same issue. Have tried the solution above, none of them works for me. :( Anyone can help?

Edited: just reopen the command prompt and rerun the ignite new myApp, will fix the issue