66 lines
981 B
Markdown
66 lines
981 B
Markdown
# move
|
|
|
|
Move an Angular application or library to another folder
|
|
|
|
## Usage
|
|
|
|
```bash
|
|
nx generate move ...
|
|
```
|
|
|
|
```bash
|
|
nx g mv ... # same
|
|
```
|
|
|
|
By default, Nx will search for `move` in the default collection provisioned in `workspace.json`.
|
|
|
|
You can specify the collection explicitly as follows:
|
|
|
|
```bash
|
|
nx g @nrwl/angular:move ...
|
|
```
|
|
|
|
Show what will be generated without writing to disk:
|
|
|
|
```bash
|
|
nx g move ... --dry-run
|
|
```
|
|
|
|
### Examples
|
|
|
|
Move libs/my-feature-lib to libs/shared/my-feature-lib:
|
|
|
|
```bash
|
|
nx g @nrwl/angular:move --project my-feature-lib shared/my-feature-lib
|
|
```
|
|
|
|
## Options
|
|
|
|
### destination
|
|
|
|
Type: `string`
|
|
|
|
The folder to move the Angular project into
|
|
|
|
### importPath
|
|
|
|
Type: `string`
|
|
|
|
The new import path to use in the tsconfig.base.json
|
|
|
|
### projectName
|
|
|
|
Alias(es): project
|
|
|
|
Type: `string`
|
|
|
|
The name of the Angular project to move
|
|
|
|
### updateImportPath
|
|
|
|
Default: `true`
|
|
|
|
Type: `boolean`
|
|
|
|
Should the schematic update the import path to reflect the new location?
|