yo generator ends straight away without creating any structure or error

[MuhammadTaha]

I want to create a custom generator in an empty folder.

npm 5.6.0
node 8.9.1
yo 2.0.0

[SBoudrias]

So the first prompt will call the npm API to check if the name is available. I wonder if somehow (maybe a corporate proxy or a firewall on your machine) is blocking this call and failing the process silently..?

[MuhammadTaha]

Might be a possibility but is there any way I can debug the real issue in it?

[SBoudrias]

Well, you could check the code and try to log somewhere. I don't know why the error is being silenced, but most likely a promise silence the error.

[MuhammadTaha]

Ohkay. Thanks for the guideline.

[mzmudziak]

This is also happening for me, either using company proxy or not. Exits silently after ask
ing all the prompts.

[SBoudrias]

Are you sure there's no asynchronous locks? Like a done = this.async() not being called?

[ps-from-md]

I believe this issue may be associated with the registry URL in the .npmrc file. I was having this same issue and my .npmrc was configured to use a VSTS registry path. When I commented out the VSTS registry path in the .npmrc file, everything started working.

Hope this helps!

[rdhelms]

This is happening for me as well, and clearing out .npmrc didn't seem to help

[cakriwut]

This is happening for me using following configuration:

• npm , 6.6.0
• node, 10.15.0
• yo, 2.0.5

Then I decided to downgrade yo to yo@2.0.0 , and the problem disappear. Hence it is likely compatibility issue with npm or node.

[luk355]

I am having exactly same issue with following configuration:

npm@6.9.0
node@10.15.3
yo@3.1.0
generator-generator@4.0.2