Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] - Automatically add missing nestconfig.json #17

Closed
MonsieurMan opened this issue Oct 5, 2017 · 3 comments · Fixed by #47
Closed

[FEATURE] - Automatically add missing nestconfig.json #17

MonsieurMan opened this issue Oct 5, 2017 · 3 comments · Fixed by #47
Assignees
Labels

Comments

@MonsieurMan
Copy link
Contributor

I think that we could simply ask the user if the project's using ts or es, create the config file and go on.

@thomrick thomrick self-assigned this Oct 5, 2017
@thomrick
Copy link
Contributor

thomrick commented Oct 5, 2017

Hey @MonsieurMan !

You're right !

Currently the new command just takes some arguments to create the project.
I'm working on a prompt that will take user inputs about the project configuration before create the project files (like npm init)

About the update command it should adapt the project structure according to Nest.

@thomrick thomrick added the bug label Oct 6, 2017
@thomrick thomrick changed the title Automatically add missing nestconfig.json [FEATURE] - Automatically add missing nestconfig.json Dec 20, 2017
@thomrick thomrick mentioned this issue Jan 24, 2018
@weeco
Copy link

weeco commented Sep 2, 2018

@thomrick Has this feature been removed? I get an exception trying to generate a new module in a project which has no nestcli.json

@thomrick
Copy link
Contributor

thomrick commented Sep 3, 2018

We are developing a default configuration in case their is no nest config file in the project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants