User Tools

Site Tools


entwine:setting_up_a_project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
entwine:setting_up_a_project [2016/05/19 09:04]
klembot
entwine:setting_up_a_project [2017/10/09 20:39] (current)
Line 15: Line 15:
     - On Linux, the easiest way to get there varies by your distribution.     - On Linux, the easiest way to get there varies by your distribution.
   - Type ''​npm init -y''​ and press the Enter key. npm will create a file for you called **package.json** that we'll talk about in a second.   - Type ''​npm init -y''​ and press the Enter key. npm will create a file for you called **package.json** that we'll talk about in a second.
- +    - After this step, npm will print out exactly what it writes to **package.json**. This will include a line that says ''​%%"​scripts":​ { "​test":​ "echo \"​Error:​ no test specified\"​ && exit 1" }%%''​. Although it says "​error,"​ no error has occurred -- this text is just a placeholder npm inserts into **package.json**.
-<note tip> +
-After this step, npm will print out exactly what it writes to **package.json**. This will include a line that says +
-''​%% +
-"​scripts":​ { +
-    ​"​test":​ "echo \"​Error:​ no test specified\"​ && exit 1" +
-}%% +
-''​. Although it says "​error,"​ no error has occurred -- this text is just a placeholder npm inserts into **package.json**. +
-</​note>​ +
   - Type ''​npm install %%--%%save grunt load-grunt-tasks grunt-entwine''​ and press Enter. npm will think for a moment, then install Grunt and Entwine for you.   - Type ''​npm install %%--%%save grunt load-grunt-tasks grunt-entwine''​ and press Enter. npm will think for a moment, then install Grunt and Entwine for you.
- +    - npm will probably print out things like ''​npm WARN package.json @1.0.0 No description'',​ ''​npm WARN package.json @1.0.0 No repository field'',​ and ''​npm WARN package.json @1.0.0 No README data''​ whenever you ask it to install packages. You can ignore these. There are some extra files, like a README, that npm suggests you create, but they aren't necessary for using npm.
-<note tip> +
-npm will probably print out things like ''​npm WARN package.json @1.0.0 No description'',​ ''​npm WARN package.json @1.0.0 No repository field'',​ and ''​npm WARN package.json @1.0.0 No README data''​ whenever you ask it to install packages. You can ignore these. There are some extra files, like a README, that npm suggests you create, but they aren't necessary for using npm. +
-</​note>​ +
   - Create a folder named **src** inside the project folder. We don't need to create **build** or **dist**, but it doesn'​t hurt. Grunt will eventually create them for us as needed.   - Create a folder named **src** inside the project folder. We don't need to create **build** or **dist**, but it doesn'​t hurt. Grunt will eventually create them for us as needed.
     - You can do this from the terminal window by typing ''​mkdir src''​ and pressing Enter, or just create the folder the way you normally would.     - You can do this from the terminal window by typing ''​mkdir src''​ and pressing Enter, or just create the folder the way you normally would.
entwine/setting_up_a_project.txt · Last modified: 2017/10/09 20:39 (external edit)