Using "@nrwl/nx-plugin": "15.9.4"
Is there option make generated plugin not buildable? Because if I remove "build" from project.json (to disable option of building library), it becomes unbuildable but I lose option in menu of generating lib, when using generator in this plugin.
Like if I create generator with name "lib" and use command "nx g lib some-name", I get options of what generator I exactly need to use (because there is collision with existing generators)
Which generator would you like to use? …
@nrwl/angular:library
@nrwl/js:library
@schematics/angular:library
But I cant see there variant of my generator.
I need to choose option None of the above and write project name of my generator to use it.
This behavior is observed when I remove "build" from project.json, if I add "build", everything is OK, but lib is now buildable.
So question is, how can I disable build and don't lose help option what generator to chose in generator menu when collisions of generators happens?
Using "@nrwl/nx-plugin": "15.9.4"
Is there option make generated plugin not buildable? Because if I remove "build" from project.json (to disable option of building library), it becomes unbuildable but I lose option in menu of generating lib, when using generator in this plugin.
Like if I create generator with name "lib" and use command "nx g lib some-name", I get options of what generator I exactly need to use (because there is collision with existing generators)
Which generator would you like to use? …
@nrwl/angular:library
@nrwl/js:library
@schematics/angular:library
But I cant see there variant of my generator.
I need to choose option None of the above and write project name of my generator to use it.
This behavior is observed when I remove "build" from project.json, if I add "build", everything is OK, but lib is now buildable.
So question is, how can I disable build and don't lose help option what generator to chose in generator menu when collisions of generators happens?