@nx/expoSee schema

@nx/expo:application

Create an Expo Application for Nx.

Usage

1nx generate application ... 2
1nx g app ... #same 2

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

You can specify the collection explicitly as follows:

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

Show what will be generated without writing to disk:

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

Examples

Generate apps/nested/myapp:

1nx g @nx/expo:app myapp --directory=nested 2

Use class components instead of functional components:

1nx g @nx/expo:app myapp --classComponent 2

Options

directory

Required
string

The directory of the new application.

e2eTestRunner

string
Default: none
Accepted values: playwright, cypress, detox, none

Adds the specified e2e test runner

linter

string
Default: none
Accepted values: eslint, none

The tool to use for running lint checks.

name

string
Pattern: ^[a-zA-Z][^:]*$

The name of the application.

unitTestRunner

string
Default: none
Accepted values: jest, none

Test runner to use for unit tests

displayName

string

The display name to show in the application. Defaults to name.

js

boolean
Default: false

Generate JavaScript files rather than TypeScript files

setParserOptionsProject

boolean
Default: false

Whether or not to configure the ESLint "parserOptions.project" option. We do not do this by default for lint performance reasons.

skipPackageJson

boolean
Default: false

Do not add dependencies to package.json.

tags

t
string

Add tags to the application (used for linting)

useProjectJson

boolean

Use a project.json configuration file instead of inlining the Nx configuration in the package.json file.

skipFormat

Internal
boolean
Default: false

Skip formatting files

standaloneConfig

Deprecated
boolean
Default: true

Split the project configuration into <projectRoot>/project.json rather than including it inside workspace.json.

Nx only supports standaloneConfig