Skip to content

Commit d4453c3

Browse files
Merge pull request SharePoint#7189 from andrewconnell/issue7163
update to make docs less "point-in-time"
2 parents 631c0b5 + e63635d commit d4453c3

File tree

1 file changed

+7
-22
lines changed

1 file changed

+7
-22
lines changed

docs/spfx/toolchain/scaffolding-projects-using-yeoman-sharepoint-generator.md

Lines changed: 7 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,9 @@
11
---
22
title: Scaffold projects by using Yeoman SharePoint generator
33
description: Use the Yeoman SharePoint generator to scaffold new client-side solution projects to build, package, and deploy SharePoint solutions.
4-
ms.date: 11/10/2020
4+
ms.date: 07/20/2021
55
ms.prod: sharepoint
66
---
7-
87
# Scaffold projects by using Yeoman SharePoint generator
98

109
[Yeoman](http://yeoman.io/) helps you to kickstart new projects, prescribing best practices and tools to help you stay productive. Using the Yeoman SharePoint generator, developers are able to scaffold new client-side solution projects to build, package, and deploy SharePoint solutions. The generator provides common build tools, boilerplate code, and a common playground website to host web parts for testing.
@@ -46,25 +45,11 @@ yo @microsoft/sharepoint --help
4645

4746
### Command-line options**
4847

49-
Option | Description
50-
-----|------
51-
`--help`|Print the generator's options and usage.
52-
`--skip-cache`|Do not remember prompt answers. Default: *false*.
53-
`--skip-install`|Do not automatically install dependencies. Default: *false*.
54-
`--component-type`|The type of component. Currently "webpart", "extension", or "library" is supported.
55-
`--component-description`|Description of the component.
56-
`--component-name`|Name of the component.
57-
`--framework`|Framework to use for the solution. Choose one from "none", "react", "knockout".
58-
`--plusbeta`| Use the beta packages. Scaffolding should be done with @plusbeta
59-
`--extension-type`|The type of extension: Currently ApplicationCustomizer, FieldCustomizer, ListViewCommandSet.
60-
`--solution-name`|Client-side solution name, as well as folder name.
61-
`--environment`|The target environment for the solution. Either "onprem", "onprem19" or "spo".
62-
`--package-manager`|The package manager for the solution. Options are: "npm", "pnpm", or "yarn". Default: *npm*
63-
`--skip-feature-deployment`|If specified, allow the tenant admin the choice of being able to deploy the components to all sites immediately without running any feature deployment or adding apps in sites. Default: *false*.
64-
`--is-___domain-isolated`|If 'y', web part will be rendered in isolated ___domain using IFrame. If set to "y", sets the component type as web part.
65-
66-
> [!WARNING]
67-
> `skip-feature-deployment` command line support was introduced with the SharePoint Framework v1.5. This option was previously a command line argument called `skipFeatureDeployment`. Also `solution-name`, `extension-type`, `component-type`, `component-description` and `component-name` have been renamed.
48+
To view a list of the command line options, pass the `--help` argument when executing the generator:
49+
50+
```console
51+
yo @microsoft/sharepoint --help
52+
```
6853

6954
Following is an example of a command that creates a solution called "hello-world" with:
7055

@@ -83,7 +68,7 @@ yo @microsoft/sharepoint
8368
--component-description "HelloWorld web part"
8469
--skip-install
8570
--environment "spo"
86-
--skip-feature-deployment true
71+
--skip-feature-deployment
8772
```
8873

8974
> [!NOTE]

0 commit comments

Comments
 (0)