You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/generated/packages/nx-plugin/documents/overview.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -155,3 +155,9 @@ To make sure that assets are copied to the dist folder, open the plugin's `proje
155
155
## Using your Nx Plugin
156
156
157
157
To use your plugin, simply list it in `nx.json` or use its generators and executors as you would for any other plugin. This could look like `nx g @my-org/my-plugin:lib` for generators or `"executor": "@my-org/my-plugin:build"` for executors. It should be usable in all of the same ways as published plugins in your local workspace immediately after generating it. This includes setting it up as the default collection in `nx.json`, which would allow you to run `nx g lib` and hit your plugin's generator.
158
+
159
+
{% callout type="warning" title="string" %}
160
+
161
+
Nx uses the paths from tsconfig.base.json when running plugins locally, but uses the recommended tsconfig for node 16 for other compiler options. See https://github.com/tsconfig/bases/blob/main/bases/node16.json
Copy file name to clipboardExpand all lines: docs/shared/packages/nx-plugin/nx-plugin.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -155,3 +155,9 @@ To make sure that assets are copied to the dist folder, open the plugin's `proje
155
155
## Using your Nx Plugin
156
156
157
157
To use your plugin, simply list it in `nx.json` or use its generators and executors as you would for any other plugin. This could look like `nx g @my-org/my-plugin:lib` for generators or `"executor": "@my-org/my-plugin:build"` for executors. It should be usable in all of the same ways as published plugins in your local workspace immediately after generating it. This includes setting it up as the default collection in `nx.json`, which would allow you to run `nx g lib` and hit your plugin's generator.
158
+
159
+
{% callout type="warning" title="string" %}
160
+
161
+
Nx uses the paths from tsconfig.base.json when running plugins locally, but uses the recommended tsconfig for node 16 for other compiler options. See https://github.com/tsconfig/bases/blob/main/bases/node16.json
Copy file name to clipboardExpand all lines: docs/shared/recipes/generators/local-generators.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,6 +95,12 @@ To run a generator, invoke the `nx generate` command with the name of the genera
95
95
nx generate @myorg/my-plugin:my-generator mylib
96
96
```
97
97
98
+
{% callout type="warning" title="string" %}
99
+
100
+
Nx uses the paths from `tsconfig.base.json` when running plugins locally, but uses the recommended tsconfig for node 16 for other compiler options. See https://github.com/tsconfig/bases/blob/main/bases/node16.json
Copy file name to clipboardExpand all lines: docs/shared/recipes/plugins/local-executors.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -134,6 +134,12 @@ Options: {
134
134
Hello World
135
135
```
136
136
137
+
{% callout type="warning" title="string" %}
138
+
139
+
Nx uses the paths from `tsconfig.base.json` when running plugins locally, but uses the recommended tsconfig for node 16 for other compiler options. See https://github.com/tsconfig/bases/blob/main/bases/node16.json
140
+
141
+
{% /callout %}
142
+
137
143
## Using Node Child Process
138
144
139
145
[Node’s `childProcess`](https://nodejs.org/api/child_process.html) is often useful in executors.
0 commit comments