Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Vue CLI fails on Windows Powershell

See original GitHub issue

Version

3.4.0

Environment info

Environment Info:

  System:
    OS: Windows 10
    CPU: (16) x64 AMD Ryzen 7 1700X Eight-Core Processor
  Binaries:
    Node: 11.9.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.13.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.5.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: 44.17763.1.0
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce

Install Vue CLI using npm by running npm i -g @vue/cli Open powershell as either standard or admin user. run vue create test in powershell

What is expected?

Vue should run its cli to create a new project without errors

What is actually happening?

Vue CLI fails in only powershell due to apparent syntax errors. It appears to work fine in cmd.

PS C:\Users\natty> vue create test
At C:\Users\natty\AppData\Local\Yarn\bin\vue.ps1:5 char:13
      *CYGWIN*) basedir=`cygpath -w "$basedir"`;;
              ~
Unexpected token ')' in expression or statement.
At C:\Users\natty\AppData\Local\Yarn\bin\vue.ps1:8 char:3
  if [ -x "$basedir/pwsh" ]; then
    ~
Missing '(' after 'if' in if statement.
At C:\Users\natty\AppData\Local\Yarn\bin\vue.ps1:8 char:5
  if [ -x "$basedir/pwsh" ]; then
      ~
Missing type name after '['.
At C:\Users\natty\AppData\Local\Yarn\bin\vue.ps1:9 char:20
  ... sedir/pwsh"  "$basedir/../Data/global/node_modules/.bin/vue.ps1" "$@"
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Unexpected token '"$basedir/../Data/global/node_modules/.bin/vue.ps1"' in expression or statement.
At C:\Users\natty\AppData\Local\Yarn\bin\vue.ps1:9 char:72
  ... sedir/pwsh"  "$basedir/../Data/global/node_modules/.bin/vue.ps1" "$@"
                                                                       ~~~~
Unexpected token '"$@"' in expression or statement.
      CategoryInfo          : ParserError: (:) [], ParseException
      FullyQualifiedErrorId : UnexpectedToken

PS C:\Users\natty>

Issue Analytics

State:
Created 5 years ago
Comments:25 (1 by maintainers)

Top GitHub Comments

155reactions

Hooponoponocommented, Dec 19, 2019

my work-around: Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope CurrentUser

91reactions

Flygenringcommented, Feb 19, 2019

It might be slightly misleading to use NPM in the “Steps to reproduce” when the issue is related to a specific version of Yarn.

Also, to circumvent the issue until it is fixed, you can just call the .cmd-shim directly to avoid the faulty PowerShell-shim, i.e. vue.cmd create test.