Description
Description
When using Nx and Nx Console in an enterprise application, the command overview in Nx Console can become quite cluttered. This is just one example of the challenges teams face when dealing with large monorepos.
I would like to request a feature that allows configuring Nx Console behavior directly from the nx.json at the workspace root. This would give teams more control over the visibility and organization of commands in Nx Console, improving the developer experience across the board.
An example configuration might look like this:
{
//...
"nxConsole": {
"commands": {
"exclude": ["dev", "build", "*-ci-*"] // Exclude 'dev', 'build', and any command containing '-ci-' from the "COMMON NX COMMANDS" section
}
}
//...
}This feature could open up a wide range of configuration possibilities for customizing how Nx Console displays and organizes available commands.
Motivation
Prevent command overflow and improve usability in large workspaces.
Suggested Implementation
Allow nx.json to include an nxConsole section for customizing which commands to display or hide. Wildcards could be supported for pattern-based filtering.
Alternate Implementations
Alternatively, a dedicated nx-console.config.json file could be used to manage Nx Console settings independently from nx.json.