Open mkvlrn opened 5 months ago
as of now you can run npm init nest
in order to generate a really tiny standard nestjs project. See the code here: https://github.com/micalevisk/create-nest
@micalevisk this is VERY impressive, I love it!
The one thing I would like to suggest is to make it aware of pnpm, because, even though running pnpm create nest
worked just fine, it installed dependencies with npm.
Edit: @micalevisk issue created
I'd suggest:
--skip-tests Do not generate testing files for the new project.
inspired by Angular CLI.
This would set generateOptions.spec
to false
as well
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
Not related to a problem, just a suggestion to add more flexibility when creating new projects with the CLI.
Describe the solution you'd like
I would like to be able to use options in the CLI when creating a new project in order to not add features that are currently added to all projects.
The features would be testing (no Jest, no Supertest, no testing configuration, no automatic spec creation, no test scripts in package.json) and linting (no Eslint and no Eslint configuration).
Teachability, documentation, adoption, migration strategy
Something like
nest new --skip-testing --skip-linting
to not install the packages and skip the configurations would be excellent.It wouldn't change the default behavior of the CLI, adding just flags for an opt-in, more customized CLI experience.
What is the motivation / use case for changing the behavior?