Feature request: Allow plugin-specific root directory configuration (e.g. jsRoot for @nx/js)

[NoamGaash]

Summary

Currently, Nx plugins like @nx/js assume the workspace root (where nx.json resides) as the root for all project discovery and operations. This creates friction in polyglot or multi-root monorepos, where different languages or ecosystems (e.g., JS, Java) are organized under their own subdirectories.

Proposal

Add a configuration option to plugins (starting with @nx/js) to specify a root directory for that plugin's operations (e.g., jsRoot). Example configuration in nx.json:

{
  "pluginsConfig": {
    "@nx/js": {
      "jsRoot": "monorepo-js"
    },
    "@jnxplus/nx-maven": {
      "javaRoot": "monorepo-java"
    }
  }
}

When set, the plugin should:

• Discover projects, dependencies, and config files (like package.json) relative to jsRoot, not the workspace root.
• Place generated projects/files under jsRoot by default.
• Fall back to the workspace root if the option is not set (for backwards compatibility).

Why

• Reduces risk: No breaking changes to Nx core; only plugin code changes.
• Enables polyglot monorepos: Each language ecosystem can be managed independently, but orchestrated by Nx.
• Incremental adoption: Each plugin can add this support as needed.

Example use case

A monorepo has the following structure:

/
  nx.json
  monorepo-js/
    package.json
    apps/
    libs/
  monorepo-java/
    ...

Developers want @nx/js to only operate within monorepo-js, and a Java plugin to operate within monorepo-java.

Request

• Please add support for a plugin-level root option (e.g. jsRoot) for @nx/js and consider similar options for other official plugins.
• Document usage and migration path.

Thank you for considering this enhancement!