@nx/expo:component

Create a Expo Component for Nx.

Usage

1nx generate component ... 2
1nx g c ... #same 2

By default, Nx will search for component in the default collection provisioned in workspace.json.

You can specify the collection explicitly as follows:

1nx g @nx/expo:component ... 2

Show what will be generated without writing to disk:

1nx g component ... --dry-run 2

Examples

Generate a component in the mylib library:

1g @nx/expo:component my-component --directory=mylib/my-component 2

Generate a class component in the mylib library:

1g @nx/expo:component my-component --directory=mylib/my-component --classComponent 2

Options

name

Required
string

The name of the component.

directory

string

The directory at which to create the component file. When --nameAndDirectoryFormat=as-provided, it will be relative to the current working directory. Otherwise, it will be relative to the project root.

classComponent

C
boolean
Default: false

Use class components instead of functional component.

export

e
boolean
Default: false

When true, the component is exported from the project index.ts (if it exists).

js

boolean
Default: false

Generate JavaScript files rather than TypeScript files.

nameAndDirectoryFormat

string
Accepted values: as-provided, derived

Whether to generate the component in the directory as provided, relative to the current working directory and ignoring the project (as-provided) or generate it using the project and directory relative to the workspace root (derived).

skipTests

boolean
Default: false

When true, does not create "spec.ts" test files for the new component.

skipFormat

Internal
boolean
Default: false

Skip formatting files.