-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Create Setup command #148
Comments
what did you think about changing package.json name properties and parent directory name with this setup command ? |
Changing the package.json name makes a lot of sense. People can already specify the name of the directory themselves when cloning, so not too worried about that. |
|
@j5v Dedicated setup scripts are rare - traditionally such tasks would be handled by something like a Yeoman generator, but I've been trying to avoid going that route. Regarding running npm install - I agree that people understand the need, just figured it might as well all be handled via one command. |
I am planning on taking a whack at this. A couple quick thoughts:
|
@gargrave Great! Good questions. I wouldn't worry about initializing a new repo since not everyone uses Git. I think prompting for package.json would be really slick and helpful. |
Thanks, Cory. I should have a PR for you sometime in the very near future. |
This command can do the following:
The text was updated successfully, but these errors were encountered: