-
Notifications
You must be signed in to change notification settings - Fork 204
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
Unable to Create New App: Tab with SPFx #12143
Comments
@ungsdev Thanks for reporting this issue to us. We're working on it and will update to you soon. |
@ungsdev The fix has been merged and please expect that in our next prerelease. I'll close this one first and feel free to reopen if it doesn't work with next build. |
To someone who needs an immediate alternative: You can create a new SPFx-based tab app using the teamsapp CLI.
|
what if you are adding a new SPFX web part as a tab in an existing teams toolkit project that has other spfx tabs? |
@React365-Chris You could try |
I tried that first. I use the CLI more than VSCode. I have the same error, which is unfixable. |
@React365-Chris Yes, I just checked and that's because TTK will first detect globally installed SPFx version which will cause failure due to nodejs/node#52554 (comment) while |
Describe the bug
When trying to create a new SPFx-based tab app, the following error occurs.
My SPFx environment is set up correctly according to the documentation provided in the error message. In fact, I have been working well with it until recently.
Here are the Node version and the list of globally installed Node modules in my environment.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The new app should be created without any errors.
Screenshots
If applicable, add screenshots to help explain your problem.
VS Code Extension Information (please complete the following information):
Additional context
Additionally, the following error occurs when selecting the ‘Use globally installed SPFx’ option instead 'Install the latest SPFx locally in Teams Toolkit directory'.
It seems there is an issue with finding the globally installed Node modules in the environment. This might be related to the issue below.
nodejs/node#52554 (comment)
The text was updated successfully, but these errors were encountered: