title: Loopback loading config files for the wrong NODE_ENV
body: <p>I am very confused by this unexpected behavior from Loopback.</p>
  
  <p>I have this logged from my Loopback server:</p>
  
  <pre><code>SFOC02Q106HG8WM:crucible-poc-discovery t_millal$ NODE_ENV=test node .
   =&gt; Loopback is loading filename =&gt;  /Users/t_millal/WebstormProjects/a/crucible-poc-discovery/server/config.local.js
   =&gt; Loopback is loading filename =&gt;  /Users/t_millal/WebstormProjects/a/crucible-poc-discovery/server/config.test.js
   =&gt; Loopback is loading filename =&gt;  /Users/t_millal/WebstormProjects/a/crucible-poc-discovery/server/datasources.local.js
   =&gt; Loopback is loading filename =&gt;  /Users/t_millal/WebstormProjects/a/crucible-poc-discovery/server/get-local-datasources.js
   =&gt; Loopback is loading filename =&gt;  /Users/t_millal/WebstormProjects/a/crucible-poc-discovery/server/datasources.test.js
  </code></pre>
  
  <p>I have specified <code>NODE_ENV=test</code></p>
  
  <p>why does Loopback still load:</p>
  
  <p><code>server/config.local.js</code> and <code>server/datasources.local.js</code>?</p>
  
  <p>isn't that a bug? Is it simply because l comes before t in the alphabet?
  Seems wrong...</p>