Generate UI cannot resolve generators at secondary entry point

[koliveira15]

Current Behavior

Generate UI cannot resolve generators that are setup as secondary entry points

Expected Behavior

Generate UI resolves generators that are setup as secondary entry points

Steps to Reproduce

Minimal Repo

1. Open Generate UI
2. Select the @myorg/nx-plugin:library generator
3. Input a name
4. Nx Console Errors
5. Run the same generator, but via a cli command & its entry point:

   npx nx g @myorg/nx-plugin/adapters:library --name foo --dryRun

6. Generator resolves successfully

Failure Logs / Images / Videos

Log:

Cannot find module '@myorg/nx-plugin/package.json'
Require stack:
- C:\Users\koliv\git\myorg\node_modules\nx\src\utils\package-json.js
- C:\Users\koliv\git\myorg\node_modules\nx\src\project-graph\plugins\loader.js
- C:\Users\koliv\git\myorg\node_modules\nx\src\project-graph\plugins\index.js
- C:\Users\koliv\git\myorg\node_modules\nx\src\command-line\run\executor-utils.js
- C:\Users\koliv\git\myorg\node_modules\nx\src\devkit-internals.js
- C:\Users\koliv\git\myorg\node_modules\nx\src\utils\assert-workspace-validity.js
- C:\Users\koliv\git\myorg\node_modules\nx\src\project-graph\build-project-graph.js
- C:\Users\koliv\git\myorg\node_modules\nx\src\project-graph\project-graph.js
- C:\Users\koliv\git\myorg\node_modules\nx\src\project-graph\file-utils.js
- C:\Users\koliv\git\myorg\node_modules\nx\src\utils\package-manager.js
- C:\Users\koliv\git\myorg\node_modules\nx\src\utils\child-process.js
- C:\Users\koliv\git\myorg\node_modules\nx\src\command-line\migrate\command-object.js
- C:\Users\koliv\git\myorg\node_modules\nx\src\command-line\nx-commands.js
- C:\Users\koliv\git\myorg\node_modules\nx\bin\init-local.js
- C:\Users\koliv\git\myorg\node_modules\nx\bin\nx.js
Pass --verbose to see the stacktrace.

Jetbrains

VSCode

Environment

Issue occurs on any OS

Nx Report:

 NX   Report complete - copy this into the issue template

Node           : 18.20.3
OS             : win32-x64
Native Target  : x86_64-windows
npm            : 10.7.0

nx                 : 19.8.14
@nx/js             : 19.8.14
@nx/jest           : 19.8.14
@nx/linter         : 19.8.14
@nx/eslint         : 19.8.14
@nx/workspace      : 19.8.14
@nx/devkit         : 19.8.14
@nx/eslint-plugin  : 19.8.14
@nx/plugin         : 19.8.14
@nrwl/tao          : 19.8.14
typescript         : 5.5.4

• WebStorm 2025.1
  • Nx Console version: 1.31.0
• VSCode version: 1.99.3
  • Nx Console version: 18.45.2

[AgentEnder]

Hey there - I don't think this is console related as the same thing would happen when running via Nx CLI.

I think this is just something that's not supported right now though, it is an interesting idea. I'm going to transfer this to the Nx repo and mark it as a feature request.

[AgentEnder]

To clarify a bit further the bit before the : isn't meant to be an import path, its meant to be either:

• A package name
• A path to a package.json file

To support arbitrary import paths there would be a bit harder and perhaps a bit wonky looking. Generally, to scope different generator collections I'd just recommend fully separate plugins

[koliveira15]

Hey there - I don't think this is console related as the same thing would happen when running via Nx CLI.

I think this is just something that's not supported right now though, it is an interesting idea. I'm going to transfer this to the Nx repo and mark it as a feature request.

Hi @AgentEnder! Thanks for looking at this. Just be clear, the generator does work with secondary entry point in the package name via the Nx CLI generator (see below). That made me think this issue is specific to the console rather than a Nx issue.

npx nx g @myorg/nx-plugin/adapters:library --name foo --dryRun

[MaxKless]

Hmmm so I cloned your repro (thanks btw, very useful) and it looks like both instances are broken... going via nx console & nx cli

Is this different for you in the minimal repro as well? Or is there maybe something else going on in your case?

[koliveira15]

Hmmm so I cloned your repro (thanks btw, very useful) and it looks like both instances are broken... going via nx console & nx cli

Is this different for you in the minimal repro as well? Or is there maybe something else going on in your case?

Hi @MaxKless ! Thanks for looking at this. In your first screenshot, the CLI command is missing the /adapters portion. The full CLI command which works for me is:

npx nx g @myorg/nx-plugin/adapters:library --name foo --dryRun

[MaxKless]

Ah that makes sense... so the issue is in the loading of the generator. When nx console shows the generate UI, it retrieves the generator name and that's already wrong. So when it executes it later, it will also be wrong.... that should be fixable, I'll look into it tomorrow