Skip to content
This repository has been archived by the owner on Jan 31, 2023. It is now read-only.

Yeoman generator is not detected correctly #436

Closed
piaste opened this issue Jan 2, 2019 · 1 comment
Closed

Yeoman generator is not detected correctly #436

piaste opened this issue Jan 2, 2019 · 1 comment
Assignees
Labels
bug Something isn't working external sev2

Comments

@piaste
Copy link

piaste commented Jan 2, 2019

After using the Create smart contract project and choosing language/folder/window options, the extension exits with the following message:

Error: You don't seem to have a generator with the name “fabric:contract” installed.
But help is on the way:

You can see available generators via npm search yeoman-generator or via http://yeoman.io/generators/. 
Install them with npm install generator-fabric:contract.

To see all your installed generators run yo without any arguments. Adding the --help option will also show subgenerators. 

If yo cannot find the generator, run yo doctor to troubleshoot your system.

However, the fabric generator is installed. Indeed, if I open the terminal and run yo fabric:contract from the current folder, the generator runs without problems.

Perhaps some environment option is not being passed to yo correctly? Let me know if there is any diagnostic output I can provide.

Environment:

Win10 x64
Node v11.6.0 (had the same problem with v8)
Npm v6.5
Yeoman v2.0.5
VSCode v1.30.1

@cazfletch cazfletch added the bug Something isn't working label Jan 3, 2019
@cazfletch cazfletch added the sev2 label Jan 18, 2019
@sstone1 sstone1 self-assigned this Jan 22, 2019
sstone1 pushed a commit to sstone1/blockchain-vscode-extension that referenced this issue Jan 22, 2019
Signed-off-by: Simon Stone <sstone1@uk.ibm.com>
sstone1 pushed a commit to sstone1/blockchain-vscode-extension that referenced this issue Jan 22, 2019
Signed-off-by: Simon Stone <sstone1@uk.ibm.com>
sstone1 pushed a commit to sstone1/blockchain-vscode-extension that referenced this issue Jan 24, 2019
sstone1 pushed a commit to sstone1/blockchain-vscode-extension that referenced this issue Jan 24, 2019
Signed-off-by: Simon Stone <sstone1@uk.ibm.com>
sstone1 pushed a commit that referenced this issue Jan 24, 2019
Separate test for npm and yo (resolves #436)
@suil
Copy link

suil commented Mar 12, 2019

still have the same issue in windows environment with version of v0.3.1.
has the change been published to vscode marketplace yet?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working external sev2
Projects
None yet
Development

No branches or pull requests

5 participants