@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 ...
2
1nx g c ... #same
2
By 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 ...
2
Show what will be generated without writing to disk:
1nx g component ... --dry-run
2
Generate a component in the mylib library:
1g @nx/expo:component my-component --project=mylib
2
Generate a class component in the mylib library:
1g @nx/expo:component my-component --project=mylib --classComponent
2
The 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.
false
Use class components instead of functional component.
false
When true, the component is exported from the project index.ts (if it exists).
false
Generate JavaScript files rather than TypeScript files.
as-provided
, derived
Whether 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
).
false
When true, does not create "spec.ts" test files for the new component.
false
Skip formatting files.
false
Create 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.
false
Use 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.