I realize that its easy to manage environment variables, but my argument is that the application does not depend on the PORT env variable. If its undefined EAK uses a reasonable default. For people just jumping into EAK that are unfamiliar with build tools, grunt, node etc debugging a conflicting ENV variable might seem overwhelming. Especially when the ENV variable  is generic PORT vs EAK_PORT, undocumented, and not required in the first place.

But enough bike shedding. I changed the code to so that the task aborts and logs an error. This will remind me that I have conflicting ENV variables which is an improvement.

Thanks