# 01 - Nodemon Intro

In this module, we'll set up Nodemon for allowing us to more easily make changes to our server code.

## Description

When you make a change to code on the client side, you just have to refresh the web page to see the effect of that change. With a server, however, it gets a little more complicated. Any changes that you make won't take effect until you stop and restart the server. When you're testing routes or endpoints and making minute changes over and over, that constant stop/start routine can get kind of ridiculous. Fortunately, we have a tool that will automatically restart your server every time you save a file: Nodemon.

## Setup

1.  In any directory, run `npm install -g nodemon`. This installs Nodemon globally on your machine. Note to Mac users: use sudo:

    `sudo npm install -g nodemon`
2. Go into the server directory (where the `package.json` file is visible)  run `npm install --save-dev nodemon`. This saves Nodemon to your `devDependencies` in `package.json`.
3.  Still in the server directory, run `nodemon app.js`. This should start the server up. You should see this:

    ![nodemon](https://785407262-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LAU8YfspjIVOP2BrMNl%2F-LAU8cHEwYbpO3Obye5i%2F-LAU8jQAi678cHzt-SW9%2Fnodemon.png?generation=1524162312189402\&alt=media)
4. The app is now running. You can stop the app with `ctrl + c`.
5. Practice running the app with Nodemon by starting it back up with the command. You can push up arrow while in your terminal to get it back quickly. &#x20;
6.  With the server running and with Nodemon started, change the console.log statement in `app.js` to a new phrase. Try using this:

    ```javascript
    app.listen(3000, function(){
     console.log('Hey man!!!')
    });
    ```
7. Press save. `nodemon` should fire back up, and you should see the new `console.log()` statement in your terminal.
