@nrwl/expoSee schema

@nrwl/expo:application

Create an Expo Application for Nx.

Usage

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

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

You can specify the collection explicitly as follows:

nx g @nrwl/expo:application ...

Show what will be generated without writing to disk:

nx g application ... --dry-run

Examples

Generate apps/nested/myapp:

g @nrwl/expo:app myapp --directory=nested

Use class components instead of functional components:

g @nrwl/expo:app myapp --classComponent

Options

name

Required
string

The name of the application.

directory

string

The directory of the new application.

displayName

string

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

e2eTestRunner

string
Default: detox
Accepted values: detox, none

Adds the specified e2e test runner

js

boolean
Default: false

Generate JavaScript files rather than TypeScript files

linter

string
Default: eslint
Accepted values: eslint

The tool to use for running lint checks.

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.

tags

t
string

Add tags to the application (used for linting)

unitTestRunner

string
Default: jest
Accepted values: jest, none

Test runner to use for unit tests

skipFormat

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