Errors Creating First Project after Installing Jovo v4 CLI

[rmtuckerphx]

I'm submitting a...

• [ x ] Bug report
• Feature request
• Documentation issue or request
• Other... Please describe:

Expected Behavior

I should be able to execute jovov4 new myproj and jovov4 run

Current Behavior

I've installed and re-installed jovov4 cli multiple times following: $ npm install -g @jovotech/cli

The first time everything looked like it installed correctly and even got back a version number:

$ npm install -g @jovotech/cli
Debugger listening on ws://127.0.0.1:56046/56ddd1e4-b299-45bd-a6a5-f8fa6dce21ba
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
C:\Users\mark\AppData\Roaming\npm\jovov4 -> C:\Users\mark\AppData\Roaming\npm\node_modules\@jo

> @jovotech/cli@4.0.0-beta.4 postinstall C:\Users\mark\AppData\Roaming\npm\node_modules\@jovot
> node bin/postinstall

Debugger listening on ws://127.0.0.1:56066/08318acb-16f2-44de-bfaf-3d04050cbf60
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Installing CLI Commands
[####################] @jovotech/cli-command-build | 100%
[####################] @jovotech/cli-command-deploy | 100%
[####################] @jovotech/cli-command-get | 100%
[####################] @jovotech/cli-command-new | 100%
[####################] @jovotech/cli-command-run | 100%

Waiting for the debugger to disconnect...
+ @jovotech/cli@4.0.0-beta.4
added 201 packages from 135 contributors in 101.035s
Waiting for the debugger to disconnect...





$ jovov4 -v
Debugger listening on ws://127.0.0.1:56125/df980527-ebdd-4249-8777-d7389b9a70ea
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.

@jovotech/cli: 4.0.0-beta.4 

Environment:
  System:
    OS: Windows 10 10.0.19043
  Binaries:
    Node: 12.13.0 - C:\Program Files\nodejs\node.EXE
    npm: 6.13.4 - C:\Program Files\nodejs\npm.CMD

Waiting for the debugger to disconnect...

And then got this error:

$ jovov4 new first
 »   Warning: new is not a jovov4 command.
Did you mean help? [y/n]: 
 »   Error: Run jovov4 help for a list of available commands.

This time around, when I execute jovov4 -v, I get this error:

$ jovov4 -v

x Error: --------------------------------------------------------------------------------
›
› Message:
›  Could not load project configuration.
› Module:
›  JovoCliCore
› Details:
›  Cannot find module '@jovotech/cli-core'
›  Require stack:
›  - C:\dev\jovo\jovo4-someApp\jovo.project.js
›  - C:\Users\mark\AppData\Roaming\npm\node_modules\@jovotech\cli\node_modules\@jovotech\cli-core\dist\Config.js
›  - C:\Users\mark\AppData\Roaming\npm\node_modules\@jovotech\cli\node_modules\@jovotech\cli-core\dist\Project.js
›  - C:\Users\mark\AppData\Roaming\npm\node_modules\@jovotech\cli\node_modules\@jovotech\cli-core\dist\index.js
›  - C:\Users\mark\AppData\Roaming\npm\node_modules\@jovotech\cli\dist\hooks\VersionHook.js
›  - C:\Users\mark\AppData\Roaming\npm\node_modules\@jovotech\cli\node_modules\@oclif\config\lib\config.js
›  - C:\Users\mark\AppData\Roaming\npm\node_modules\@jovotech\cli\node_modules\@oclif\config\lib\index.js
›  - C:\Users\mark\AppData\Roaming\npm\node_modules\@jovotech\cli\node_modules\@oclif\command\lib\command.js
›  - C:\Users\mark\AppData\Roaming\npm\node_modules\@jovotech\cli\node_modules\@oclif\command\lib\index.js
›  - C:\Users\mark\AppData\Roaming\npm\node_modules\@jovotech\cli\dist\index.js
›  - C:\Users\mark\AppData\Roaming\npm\node_modules\@jovotech\cli\bin\run
›
› If you think this is not on you, you can submit an issue here: https://github.com/jovotech/jovo-cli/issues.

The above is from a Bash Shell terminal in VSCode running on Windows 10. Another Jovo dev sent a ZIP that included a sample project and I am running the version command inside the project folder.

Error log

If you have an error log, please paste it here.

Your Environment

Environment:
System:
OS: Windows 10 10.0.19043
Binaries:
Node: 12.13.0 - C:\Program Files\nodejs\node.EXE
npm: 6.13.4 - C:\Program Files\nodejs\npm.CMD

[rmtuckerphx]

When I execute the following: npm list -g --depth=0 should I see a mix of beta.4 and beta.3 files?

+-- @jovotech/cli@4.0.0-beta.4
+-- @jovotech/cli-command-build@4.0.0-beta.3
+-- @jovotech/cli-command-deploy@4.0.0-beta.3
+-- @jovotech/cli-command-get@4.0.0-beta.3
+-- @jovotech/cli-command-new@4.0.0-beta.3
+-- @jovotech/cli-command-run@4.0.0-beta.3

[rmtuckerphx]

I even tried deleting each @jovotech/cli entry before doing a new install:

npm uninstall -g @jovotech/cli-command-run
...

[rubenaeg]

@rmtuckerphx sorry for the long delay, but I finally was able to reproduce the bug and now seem to have a solution that should work across systems and management solutions (i.e. npm, nvm, fnm, ...).