Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

yo generator ends straight away without creating any structure or error #215

Open
MuhammadTaha opened this issue Jan 15, 2018 · 10 comments
Open

Comments

@MuhammadTaha
Copy link

MuhammadTaha commented Jan 15, 2018

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

npm 5.6.0
node 8.9.1
yo 2.0.0

image

@MuhammadTaha MuhammadTaha changed the title yo generator ending straight away without creating the structure yo generator ends straight away without creating any structure or error Jan 15, 2018
@SBoudrias
Copy link
Member

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
Copy link
Author

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

@SBoudrias
Copy link
Member

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
Copy link
Author

Ohkay. Thanks for the guideline.

@mzmudziak
Copy link

mzmudziak commented Feb 26, 2018

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

@SBoudrias
Copy link
Member

SBoudrias commented Feb 27, 2018

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

@ps-from-md
Copy link

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
Copy link

rdhelms commented Apr 5, 2018

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

image

@cakriwut
Copy link

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 [email protected] , and the problem disappear. Hence it is likely compatibility issue with npm or node.

@luk355
Copy link

luk355 commented Aug 15, 2019

I am having exactly same issue with following configuration:

[email protected]
[email protected]
[email protected]
[email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants