Unable to generate custom generator

[marcore86]

Hi there,
I am quite new with generator stuff and I am just trying to create a new one but "yo generator" command is not behaving as expected.

C:\dev\generator-ionic-angular>yo generator
? Your generator name generator-ionic-angular

C:\dev\generator-ionic-angular>npm -v
5.4.2

C:\dev\generator-ionic-angular>node -v
v8.8.0

C:\dev\generator-ionic-angular>yo --version
2.0.0

I am running on Windows 10, x64.
As you can see, after the first question, the generator is just quitting and nothing has been done into folder. Am I doing something wrong?

Thanks,
Marco

[mischah]

So after hitting the enter key at the question ? Your generator name yo simply quits?
Without any error message?

[mischah]

generator-generator should create a subdirectory within your generator-ionic-angular directory.

Check the following output:

 ~/temp/huzzel
$ yo generator
? Your generator name generator-huzzel
Your generator must be inside a folder named generator-huzzel
I'll automatically create this folder.
? Description

So your issue might be caused by missing permissions.

[marcore86]

Hi @mischah , thanks to gets me back.

So after hitting the enter key at the question ? Your generator name yo simply quits?

• Yes, no error messages are shown.

I tried to run 'yo generator' into a folder with the same name, didn't work.
Also, i did try to run 'yo' command and then select 'generator' option but, after the question name i did get ' Bye from us! Chat soon.' message by yeoman team.

Thanks

[SBoudrias]

I believe we check with NPM if the name you selected exists before continuing. Any chance a corporate proxy would be blocking that request somehow?

Usually this throws and print an error when happening. That you don't get anything on the console here is really weird...

[47669079]

I have the same issue :(

[MuTsunTsai]

I'm having the same problem; after typing the name, it simply stop responding. It doesn't print any message, doesn't quit, nothing. Just stop responding. Win 10 x64 as well.

Update

Fixed after upgrading node to v.14