search

nestjs / nest-cli

CLI tool for Nest applications 🍹
https://nestjs.com
Other
1.98k stars 394 forks source link

Allow passing arguments to `nest start <app>` #1844

Closed alko89 closed 1 year ago

alko89 commented 1 year ago

Is there an existing issue that is already proposing this?

Is your feature request related to a problem? Please describe it

We have a nest monorepo project. I've recently created a cli app to help with debugging and testing. Using nest start <app> doesn't allow passing additional arguments to the monorepo CLI app.

Describe the solution you'd like

Enable passing optional arguments to Nest app using Nest CLI.

Teachability, documentation, adoption, migration strategy

No response

What is the motivation / use case for changing the behavior?

Enables more usecases and flexibility to the CLI.

kamilmysliwiec commented 1 year ago

Would you like to create a PR for this feature?

alko89 commented 1 year ago

Sure, I can look into it :+1:

kamilmysliwiec commented 1 year ago

Let's track this here https://github.com/nestjs/nest-cli/pull/1847

zackdotcomputer commented 1 year ago

This issue was not resolved by the above PR, apparently, because commands like yarn nest start sync -- --syncType=employees still fail with the error error: unknown option '--syncType'. I assume from reading the start.command file that this is because commander is not being called with allowUnknownOption enabled. I will try to make a PR to enable that.