You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
ortessel init
. Node users are used to usingnpm 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 simpletessel init
that creates the package.json for you would also suffice.The text was updated successfully, but these errors were encountered: