Nested modules about babel-plugin-rewire

[Jpunt]

I think I've figured it out and it does not seem to be an babel-plugin-rewire-issue directly. For those interested: I'm working on an isomorphic project and to have one single source of configuration i've got this module:

/*jslint node: true */
'use strict';

import _ from 'lodash';
import environment from './utils/environment';

var config;
var server;
var client;

if(environment.isServer) {
  var env = process.env.NODE_ENV || 'development';
  var shared = require('./config/' + env + '-shared.json');

  // Load config for server
  server = _.merge({}, shared, require('./config/' + env + '-server.json'));

  // Load config for client
  client = _.merge({}, shared, require('./config/' + env + '-client.json'));

  config = server;
  config.client = client; // To render in window.config later on
} else {
  config = window.config; // Return client-specific config on the client
}

export default config;

Even though I wasn't requiring this directly in the modules that I was testing, it was failing on config = window.config;. I've changed this to config = window.config || {}; and my tests (and mocks) are behaving properly now.

I guess karma, babel and/or webpack are interpreting this module anyway, even though I'm not using it in this case?

[speedskater]

Thanks @Jpunt for figuring this out.