From my experience, the `-L` option must be added to the nodemon command in order to trigger a new build in the case where source files are edited from the host.

That is, change ` nodemon --exec babel-node ./src/server.js` to ` nodemon -L --exec babel-node ./src/server.js`

Otherwise, awesome write-up.

Interesting. I can't remember having to do this, but I'll check it out next time I run babel-node with nodemon. Thanks for the tip!

Thanks for the awesome article! It helped me a bunch! One issue I am having is running the docker-compose run --rm express npm install command. I get checkPermissions Missing write access to /app/node_modules. One thing I found when googling the issue is to use --chown=node:node with the COPY command but for me this doesnt seem to work. Have your run into this? Any suggestions? Thanks!

Great article! I'm struggling with installing npm package from private npm repository (github packages). Is there a way to pass an npm auth token as an env variable before npm install command? Eg:
docker-compose run --rm express AUTH_TOKEN=xyz123 npm install

Hi! Have you tried the `-e` option? You can use it to set environment variables on one-off containers. See https://docs.docker.com/com...

I'll give it a try, thanks!

Thanks, awesome article! Could you share an idea how database migrations/seeds should be implemented?