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

"Which type of client-side component to create?" is missing "Extension" #1355

Closed
mvcsharepointdev opened this issue Jun 11, 2022 · 1 comment
Labels
needs triage Awaiting triage stale

Comments

@mvcsharepointdev
Copy link

I am using Node.js 14.18.1 (x64) and npm.

When i run D:\extensionfullstack>yo @microsoft/sharepoint I got this :-

D:\>cd D:\extensionfullstack

D:\extensionfullstack>yo @microsoft/sharepoint

     _-----_     ╭──────────────────────────╮
    |       |    │      Welcome to the      │
    |--(o)--|    │  SharePoint Client-side  │
   `---------´   │         Solution         │
    ( _´U`_ )    │     Generator@1.13.0     │
    /___A___\   /╰──────────────────────────╯
     |  ~  |
   __'.___.'__
 ´   `  |° ´ Y `

Let's create a new SharePoint solution.
? What is your solution name? extensionfullstack
? Only SharePoint Online (latest) is supported.  For earlier versions of SharePoint (2016 and 2019) please use the 1.4.1
 version of the generator. SharePoint Online only (latest)
? Where do you want to place the files? Use the current folder
? 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? Yes
? Will the components in the solution require permissions to access web APIs that are unique and not shared with other c
omponents in the tenant? Yes
? Which type of client-side component to create?
> WebPart

Where "Extension" option is missing any advice? Thanks

@mvcsharepointdev mvcsharepointdev added the needs triage Awaiting triage label Jun 11, 2022
@github-actions
Copy link
Contributor

This issue is stale because it has been open with no activity. Remove stale label or comment or this will be closed

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

No branches or pull requests

1 participant