modified 'start' script so changes to files in 'lib' trigger restart

[OmarHussainX]

First of all, thank you for this example.

I'm assuming the intended behaviour for the npm start script is that changes to lib/index.js would show (after an automatic server restart) in the server running at http://127.0.0.1:1337/

That's the behaviour I expect, and I believe this is what was intended since the README states:

...replace Hello World with Hello {{YOUR_NAME_HERE}} while our server is running.
If you visit http://127.0.0.1:1337 you should see our server greeting you.

However the provided npm start script does not do this - changes to lib/index.js are detected, and trigger a server restart, but no transpilation is done, so dist/index.js is not updated and thus changes in lib do not appear in the server.

I've revised the npm start script so that: nodemon explicitly watches lib for changes, when a change occurs lib is transpiled to dist, and then the server is restarted.

[dkarski]

@OmarHussainX I think that you could use the proposal from this answer for the issue: #38 (comment)

{
  "scripts": {
    "build": "babel -d lib src",
    "watch": "nodemon --watch src --exec yarn start",
    "start": "yarn build && yarn serve",
    "serve": "node lib/index",
    "test": "echo \"No test specified\" && exit 0"
  },
}

And then you should update READ.md https://github.com/babel/example-node-server#example-node-server-w-babel

Watching file changes with nodemon could be move after Getting ready for production use section.