Just a hobbyist programmer with an eye on new technologies. Currently helping Quasar and NestJS Frameworks, because....well.....because they're awesome! :-)
Hey Jay. Nice article. I'm using Rush currently (but am still experimenting on what to use for monorepo management) and haven't gotten to using Rush's change command yet. But, from just reading the docs, would you say it is similar to what you are achieving with changesets? rushjs.io/pages/commands/rush_change/
And in terms of building packages, you mention needing to use a Narwal package. Does Nx always need a pre-built build package, which is third party to the package itself (like using Nest's own CLI build command for a nest project)?
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.
Hey Jay. Nice article. I'm using Rush currently (but am still experimenting on what to use for monorepo management) and haven't gotten to using Rush's
changecommand yet. But, from just reading the docs, would you say it is similar to what you are achieving with changesets? rushjs.io/pages/commands/rush_change/And in terms of building packages, you mention needing to use a Narwal package. Does Nx always need a pre-built build package, which is third party to the package itself (like using Nest's own CLI build command for a nest project)?
Scott
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