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

tessel/npm init instead of mkdir node_modules #127

Open
rockbot opened this issue Jul 27, 2014 · 0 comments
Open

tessel/npm init instead of mkdir node_modules #127

rockbot opened this issue Jul 27, 2014 · 0 comments

Comments

@rockbot
Copy link

rockbot commented Jul 27, 2014

Currently, on the blinky doc page, it instructs the user to mkdir node_modules.

For the sake of consistency across node applications, I recommend that users instead be instructed to either npm init or tessel init. Node users are used to using npm init every time they're starting a new module or application, and starting a new tessel project should be no different.

If the major concern with npm init is that the questions that the init prompts ask are overwhelming to new users, a simple tessel init that creates the package.json for you would also suffice.

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

No branches or pull requests

2 participants