Sp-dev-docs: Yeoman Freeze on Windows 10

[marcorocca1973]

Hi All
my dev environment is based on Windows 10 (64bit) client, with installed

• node js 10.16.0
• latest version of yeoman, gulp and SharePoint generator (1.8.2)

But when i create new project for SharePoint online, yeoman "freeze" and nothing happens (see picture). I can only close window.

I try with other machine with Windows Server 2012 R2 and Windows Server 2016 but results is the same.
Same results when i try to clean npm cache and reinstall all components.

Could you help me?
Thanks
Marco

[msft-github-bot]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[andrewconnell]

A few followup questions:

• Is that (the screenshot) where it freezes?
• Can you run npm list -g --depth=0
• Are you running any type of antivirus that could be blocking scripts from running?

[Edzgarl]

Same here, and I tried to execute the command with parameters but it still freeze.

[rob-windsor]

I can reproduce. I completely refreshed a VM (i.e. reinstalled Node, Yeoman, Gulp, and the SPFx generator) and the generator is freezing when accepting input on the question "Do you want to allow the tenant admin the choice of being able to deploy the solution to all sites immediately without running any feature deployment or adding apps in sites?"

[cimares]

I'm seeing the same issue.. when I run Yo @microsoft/Sharepoint, it takes around 3 minutes for the Yeoman symbol to show. With the YO Debug variable set, this still takes 3 minutes to show the Debug messages.

Once the generator does display, it stops for a while after the File location choice, then stops completely at the Admin deploy choice.., No keyboard entry seems to do anything.

I've left this one running for about 20 minutes so far.

[cimares]

npm list -g --depth=0 returns:
+-- @microsoft/[email protected]
+-- [email protected]
`-- [email protected]

Running yo --version returns the version quickly, but running Yo on it's own to trigger the generator picker takes forever as well. (Although I'm not sure how quick this is usually!)

[Edzgarl]

Same with Linux ..
♥ Microdobe ♥

[andrewconnell]

@patmill Seems multiple reports all the sudden coming in about the Yeoman SPFx generator freezing up... aware of this?

[andrewconnell]

Think we've isolated to the latest version of Yeoman (2.0.6) on Windows.

Can you guys downgrade and try again?

npm install -g [email protected]

[jefmeyer]

I have the same issue with 2.0.2

[andrewconnell]

@jefmeyer did you upgrade to a version > 2.0.2, then downgrade to 2.0.2? Or have you never had a version above 2.0.2 installed?

[jefmeyer]

I just installed Yo 2.0.6 this morning, ran into the issue, saw this thread and then downgraded to 2.0.2

[andrewconnell]

now starting to smell like a downstream dependency in Yeoman... check this out: https://github.com/yeoman/yeoman/issues/1714

Check all global installs: npm list -g
Search for inquirer ... check the version. If >= 6.4.0, try installing 6.3.1: npm i -g [email protected]

I'm on macOS and not having this issue so hard for me to replicate...

[Tanddant]

Even after a npm i -g [email protected] i still get the freeze

[jefmeyer]

@andrewconnell I cleared all the NPM packages, went through the "Setup development" guide again, rolled back yo to 2.0.2 and also the inquire version, but still same freeze issue, checking after each rollback.

[rob-windsor]

@andrewconnell I installed [email protected] but 6.4.0 is still there as a dependency of Yeoman. At least it appears to be. This is where my lack of full understanding how these dependency trees work defeats me.

[rob-windsor]

@andrewconnell I dropped down to [email protected] but [email protected] is still in the dependencies.

[StfBauer]

@rob-windsor no matter which version 2.0.0 you use this won't work because how yeoman has defined their versions of inquirer in package.json. You have to move back to version 1.x.x.

The easiest way to accomplish this is to execute the following command:

npm install @microsoft/generator-sharepoint@1 -g

This should then installed an older version of the inquirer package and the generator is working again:

SPFx anyway uses a really old version of yeoman so no need to worry or update to the latest version.

It seems that this issue is related to: https://github.com/SBoudrias/Inquirer.js/issues/811

[MickNabewata]

After installing yeoman v1.8.5, spfx generator v1.8.2 has worked.
npm install yo@1 -g

But I saw the another freeze when I run the following command.
yo @microsoft/sharepoint

Instead, when I run yo and choose @microsoft/sharepoint, it's work.

thank you for everyone of this thread !

[marcorocca1973]

@MickNabewata I confirm your test
Command
yo @microsoft/SharePoint
still not working :(

But working if I choose yo and select:
@microsoft/SharePoint

[StfBauer]

@marcorocca1973 and @MickNabewata can you please share the output of:

npm ls inquirer -g

Thank you!

It could be that you have to install the generator again after downgrading to 1.8.5.

[marcorocca1973]

@StfBauer
this is my output

[cimares]

My home PC has the old generator on it and it's working fine..

[StfBauer]

The mentioned issue with the inquirer package SBoudrias/Inquirer.js#811 is now fixed and closed on their repo.

To verify it does not affect the @microsoft/generator-sharepoint anymore and it is really fixed I tested it on the following systems:

• Windows 2012 R2
• Windows 2016
• Windows 10

Using the following command line tool:

• cmd
• PowerShell

The way to get it running again should work with the following steps:

Step 1: uninstall current version (optional)

This is optional because in general step 2 should update everything to the latest version too.

npm uninstall -g yo @microsoft/generator-sharepoint

Step 2: Install @latest versions

npm install -g yo@latest @microsoft/generator-sharepoint@latest

Step 3: verify inquirer version 6.4.1

npm ls inquirer -g

This should produce an output like this:

The key part here is that inquirer version 6.4.0 is not referenced anywhere. This is the faulty version and the root cause of the issue you are facing.

[marcorocca1973]

Great!
@StfBauer I follow your step and now everything works!
Marco

[cimares]

Excellent, that should fix it for people following the "set up your development environment for SPFx" guide too then!

[andrewconnell]

Nice work @StfBauer ... looks like this only affects people who installed / upgraded Yeoman for a specific period of time. New installs starting today won’t have this issue, and if they were affected by it, reinstalling will fix.

For those new finding this issue, this is not an issue rooted in SPFx / SharePoint’s Yeoman generator. The issue is with a Yeoman dependency (Inquirer) which has since been fixed.

[roberteisenberg]

I started with the problem mentioned above with the generator freezing on the tenant input question. I then ran npm install @microsoft/generator-sharepoint@1 -g and it started to freeze on the web part name.
I uninstalled the 10.16.0 node version with NVM. Installed it again. Then followed the instructions to uninstall and reinstall the generator and now the problem is that it only asks me a subset of the questions and does not produce any output. See current node/npm version info, followed byYeomen generator output, and then Followed by the Inquirer details.

[StfBauer]

@roberteisenberg This only happens when you have a .yo-rc file in the folder or above the folder you executed the generator on and is the default behaviour. You basically add a web part or extension to an existing project.

Try it on a clean folder where neither in the folder or above is a .yo-rc file.

[mauricework]

The mentioned issue with the inquirer package SBoudrias/Inquirer.js#811 is now fixed and closed on their repo.
To verify it does not affect the @microsoft/generator-sharepoint anymore and it is really fixed I tested it on the following systems:

Windows 2012 R2
Windows 2016
Windows 10

Using the following command line tool:

cmd
PowerShell

The way to get it running again should work with the following steps:
Step 1: uninstall current version (optional)
This is optional because in general step 2 should update everything to the latest version too.
npm uninstall -g yo @microsoft/generator-sharepoint
Step 2: Install @latest versions
npm install -g yo@latest @microsoft/generator-sharepoint@latest
Step 3: verify inquirer version 6.4.1
npm ls inquirer -g
This should produce an output like this:

The key part here is that inquirer version 6.4.0 is not referenced anywhere. This is the faulty version and the root cause of the issue you are facing.

Thanks a bunch for that. Was a frustrating day when I decided to try out the instructions for the hello world web part and it hung up. Monday is going much better...:)

[andrewconnell]

@mauricework said:

Monday is going much better

Usually, you follow this statement with _"...said no one ever"_, but you have broken the internet. Nice... :P

[msft-github-bot]

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues