Restart the app if environment variables change

[quis]

Could be confusing why your changes aren’t having any effect.

Someone should probably test this before merging it 😬

cc @edwardhorsford

[gemmaleigh]

I tested this locally, when I make changes to the .env file and save them, nodemon doesn't restart the app.

[quis]

Thanks for the testing.

I’ve changed it so that it actually works in b7bf675:

Doing this using the existing file-extension-based config doesn’t work because nodemon doesn’t undestand that .env is a file with no name, and an extension of env. So I’ve removed the file-extension-based stuff entirely and rewritten it to use globbing.

Tested locally that:

• changing server.js or .env causes the app to restart
• changing a file inside node_modules doesn’t cause the app to restart

[NickColley]

I have pulled Chris' change locally and confirmed that changing a file ending with .js, .json and .env triggers nodemon to restart the application.

[NickColley]

I think all we need is an addition to the CHANGELOG under 'features'

[quis]

@NickColley done and squashed into aaf531c

[NickColley]

Sweet thanks Chris

[joelanman]

Quick thought, does this affect very first start up after install? The kit creates empty .env at that point, wonder if that triggers restart and if that's a problem

[NickColley]

@joelanman no problems from my testing.

1. delete .env
2. run npm start
3. edit .env

only restarts once when the edit is made.

[joelanman]

Looks great, thanks! Do you mind rebasing, as there's now a conflict with CHANGELOG

[36degrees]

Rebased against master.

[NickColley]

👍 to merge

[36degrees]

Thanks, @quis!