Looking back to these comments in #22:

The @lib/environment import apparently gets interpreted (when trying to use babel-node to compile and execute an ES6+ formatted script) as a module/dependency:

Error: Cannot find module '@lib/environment'

It looks like we might be able to use babel-plugin-module-resolver to achieve similar aliasing benefits, but with more control and (hopefully) more flexibility for local testing.