@nx/expo:component
Create a Expo Component for Nx.
Monorepo World: October 7, 2024Monorepo World: October 7, 2024Join us!
Create a Expo Component for Nx.
1nx generate component ...
21nx g c ... #same
2By default, Nx will search for component in the default collection provisioned in workspace.json.
You can specify the collection explicitly as follows:
1nx g @nx/expo:component ...
2Show what will be generated without writing to disk:
1nx g component ... --dry-run
2Generate a component in the mylib library:
1g @nx/expo:component my-component --project=mylib
2Generate a class component in the mylib library:
1g @nx/expo:component my-component --project=mylib --classComponent
2The name of the component.
The directory at which to create the component file. When --nameAndDirectoryFormat=as-provided, it will be relative to the current working directory. Otherwise, it will be relative to the project root.
falseUse class components instead of functional component.
falseWhen true, the component is exported from the project index.ts (if it exists).
falseGenerate JavaScript files rather than TypeScript files.
as-provided, derivedWhether to generate the component in the directory as provided, relative to the current working directory and ignoring the project (as-provided) or generate it using the project and directory relative to the workspace root (derived).
falseWhen true, does not create "spec.ts" test files for the new component.
falseSkip formatting files.
falseCreate component at the source root rather than its own directory.
Provide the directory option instead and use the as-provided format. This option will be removed in Nx v19.
The name of the project.
Provide the directory option instead and use the as-provided format. The project will be determined from the directory provided. It will be removed in Nx v20.
falseUse pascal case component file name (e.g. App.tsx).
Provide the name in pascal-case and use the as-provided format. This option will be removed in Nx v19.