@nx/plugin:plugin
Create a Plugin for Nx.
Create a Plugin for Nx.
1nx generate plugin ...
2
By default, Nx will search for plugin
in the default collection provisioned in workspace.json.
You can specify the collection explicitly as follows:
1nx g @nx/plugin:plugin ...
2
Show what will be generated without writing to disk:
1nx g plugin ... --dry-run
2
Generates an Nx plugin project called plugins-my-plugin
at libs/plugins/my-plugin
. The project will have an npm package name and import path of @myorg/my-plugin
.:
1nx g plugin my-plugin --directory=plugins --importPath=@myorg/my-plugin
2
A directory where the plugin is placed.
How the plugin will be published, like @myorg/my-awesome-plugin
. Note this must be a valid NPM name.
none
, eslint
The tool to use for running lint checks.
Plugin name
none
, jest
, vitest
Test runner to use for unit tests.
tsc
tsc
, swc
The compiler used by the build and test targets.
none
jest
, none
Test runner to use for end to end (E2E) tests.
false
Generates a boilerplate for publishing the plugin to npm.
false
Do not eslint configuration for plugin json files.
false
Whether or not to configure the ESLint parserOptions.project
option. We do not do this by default for lint performance reasons.
Add tags to the library (used for linting).
Use a project.json
configuration file instead of inlining the Nx configuration in the package.json
file.
false
Skip formatting files.
false
Do not update tsconfig.json for development experience.
true
Split the project configuration into <projectRoot>/project.json
rather than including it inside workspace.json
.
Nx only supports standaloneConfig