Enforce Usage of Custom Generators Over Default Nx Generators

[raveclassic]

I am working in a large Nx repository and we have developed custom generators to better meet our needs, as the standard generators are not suitable for our requirements. However, we are facing challenges in ensuring that all developers consistently use our custom generators instead of the default ones.

While we considered removing @nx/js from the root package.json, we found that nx g @nx/js:lib still executes because this package is installed by other plugins like @nx/vite. Since our repository uses pnpm, we expected that Nx wouldn't be able to find @nx/js.

To improve our workflow and maintain consistency, we would like to implement a mechanism that prevents the usage of default Nx generators in favor of our custom ones.

For example, one possible implementation could be disabling the generator in the root nx.json file under the generators section (pseudo):

{
  "generators": {
    "@nx/js": {
      "disabled": true,
      "message": "Please use custom generator"
    }
  }
}