@aws/nx-plugin-mcp 1.0.0-rc.28 → 1.0.0-rc.29
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/bin/aws-nx-mcp.js
CHANGED
|
@@ -54161,6 +54161,7 @@ ${PACKAGE_MANAGERS.map((pm) => buildNxCommand("<options>", pm)).join(" - \n")}
|
|
|
54161
54161
|
- (Omit -D for production dependencies)
|
|
54162
54162
|
- When specifying project names as arguments to generators, prefer the _fully qualified_ project name, for example \`@workspace-name/project-name\`. Check the \`project.json\` file for the specific package to find its fully qualified name
|
|
54163
54163
|
- When no generator exists for a specific framework required, use the base \`ts#project\` and \`py#project\` generators and build on top.
|
|
54164
|
+
- Leave the \`--infra\` option at its default value unless the user has explicitly instructed otherwise. Generators choose a sensible default type of infrastructure to deploy the project with, so only override \`--infra\` when the user has specified a particular requirement.
|
|
54164
54165
|
|
|
54165
54166
|
## Useful Commands
|
|
54166
54167
|
|
|
@@ -108,7 +108,7 @@ You can start writing your Terraform infrastructure inside `src/main.tf`, for ex
|
|
|
108
108
|
|
|
109
109
|
### Cross project dependencies
|
|
110
110
|
|
|
111
|
-
If you wanted to execute a module from a
|
|
111
|
+
If you wanted to execute a module from a separate project (lib), you could do so as follows:
|
|
112
112
|
|
|
113
113
|
```
|
|
114
114
|
module "lib_module" {
|