Rewiring doesn't work on first javascript execution pass, only later passes

[timkindberg]

If I have the following code where I am importing something (in this case the connect function) and then using it at the top scope (not within a nested function scope):

// mycomponent.js
import { connect } from 'react-redux';

const MyComponent = () => <div>Hi</div>;

export default connect()(MyComponent);

and I try to rewire it like so:

// mycomponent.spec.js
import { MyComponent, __RewireAPI__ as TestAPI } from 'mycomponent';
import { shallow } from 'enzyme';

describe('My Component', () => {
  beforeEach(() => {
    TestAPI.__Rewire__('connect', () => (cmp) => cmp);
  });

  it('does stuff', () => {
    const wrapper = shallow(<MyComponent />);    
  });
});

In the above test case the code still throws an error talking about missing a redux store; even though I rewired the connect method to be basically a pass through that returns the component identity. All the examples on the site do not cover this sort of use case but it's very common.

Does rewire support this functionality?

[speedskater]

@timkindberg Thanks for opening the issue and sorry for the delay. But unfortunatly this is impossible to do. The reason is that you are rewireing the connect method after it has been used. There are two possible solutions I would propose:

• Move the Dump Component into a separate file
• Add a named export for the Dump Component
• Export a factory function instead of the already connected Component

Hopefully one of this solutions may help.

[timkindberg]

Man that is quite disappointing but I understand the technical limitation. I was hoping somehow since it was a Babel transpile time thing that we could figure this out.