This is a non-issue. The debugger shows the environment as a module, but let's say you pass environment.propThatExists to a function and then while debugging, you step into that function. The value will be there, even though Chrome's debugger showed it as undefined before you stepped in. This is an issue with the Chrome debugger and not with your code, so you can just ignore it.