From a (very) brief overview of the command, yeah, rush's change looks similar to the changeset tool, difference really being is it another package to bring in or already part of the toolset
Nx actually doesn't use Nest's CLI under the hood, but uses tsc or webpack where applicable. When building packages, the Typescript compiler gets used, and when building applications, usually the webpack compiler is picked (re-compiling on save is still possible). And there's ways to plug in Nest's CLI plugins (like swagger and GraphQL) to the Nx build step as well.
You could probably build your own executor if you wanted to use Nest's CLI though
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
From a (very) brief overview of the command, yeah,
rush'schangelooks similar to thechangesettool, difference really being is it another package to bring in or already part of the toolsetNx actually doesn't use Nest's CLI under the hood, but uses tsc or webpack where applicable. When building packages, the Typescript compiler gets used, and when building applications, usually the webpack compiler is picked (re-compiling on save is still possible). And there's ways to plug in Nest's CLI plugins (like swagger and GraphQL) to the Nx build step as well.
You could probably build your own executor if you wanted to use Nest's CLI though