Skip to content

Project initialization: move Jest config to a separate file #2231

Description

@OSA413

Is there an existing issue that is already proposing this?

  • I have searched the existing issues

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

I want to see the initial project created by running nest new project-name --strict with proper file structure for config files. One of the files is the Jest config.

Describe the solution you'd like

Remove config from package.json and move it to a propriate Jest config file (I personally use jest.config.ts).

Teachability, documentation, adoption, migration strategy

No response

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

This is one of the first things I do when creating a new project since I prefer keeping config files outside of the package.json file. I also inherit the typescript template for Jest to remove copy-pasted code for transforms of .ts files.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions