@nx/expo:application
Create an Expo Application for Nx.
Create an Expo Application for Nx.
1nx generate application ...
21nx g app ... #same
2By 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 ...
2Show what will be generated without writing to disk:
1nx g application ... --dry-run
2Generate apps/nested/myapp:
1g @nx/expo:app myapp --directory=nested
2Use 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.
detoxdetox, noneAdds the specified e2e test runner
falseGenerate JavaScript files rather than TypeScript files
eslinteslintThe tool to use for running lint checks.
as-provided, derivedWhether 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).
falseWhether or not to configure the ESLint "parserOptions.project" option. We do not do this by default for lint performance reasons.
falseDo not add dependencies to package.json.
Add tags to the application (used for linting)
jestjest, noneTest runner to use for unit tests
falseSkip formatting files
trueSplit the project configuration into <projectRoot>/project.json rather than including it inside workspace.json.
Nx only supports standaloneConfig