@nx/expo:application
Create an Expo Application for Nx.
The State of JS survey is live, featuring a monorepo tools sectionThe State of JS survey is live, featuring a monorepo tools sectionVote for us
Create an Expo Application for Nx.
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
Generate apps/nested/myapp:
1g @nx/expo:app myapp --directory=nested
2
Use class components instead of functional components:
1g @nx/expo:app myapp --classComponent
2
^[a-zA-Z][^:]*$
The name of the application.
The directory of the new application.
The display name to show in the application. Defaults to name.
detox
detox
, none
Adds the specified e2e test runner
false
Generate JavaScript files rather than TypeScript files
eslint
eslint
The tool to use for running lint checks.
as-provided
, derived
Whether to generate the project name and root directory as provided (as-provided
) or generate them composing their values and taking the configured layout into account (derived
).
false
Whether or not to configure the ESLint "parserOptions.project" option. We do not do this by default for lint performance reasons.
false
Do not add dependencies to package.json
.
Add tags to the application (used for linting)
jest
jest
, none
Test runner to use for unit tests
false
Skip formatting files
true
Split the project configuration into <projectRoot>/project.json
rather than including it inside workspace.json
.
Nx only supports standaloneConfig