@nx/expo:application
Create an Expo Application for Nx.
Create an Expo Application for Nx.
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 @nx/expo:application ...
Show what will be generated without writing to disk:
nx g application ... --dry-run
Generate apps/nested/myapp:
g @nx/expo:app myapp --directory=nested
Use class components instead of functional components:
g @nx/expo:app myapp --classComponent
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.
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