React.createElement: type is invalid -- expected a string but got: undefined in integration tests

Component Resolution Failure

When executing integration tests for components that rely on external module resolution or environment-specific imports, the renderer may encounter a failure where a component is imported as undefined. This typically occurs when there is a mismatch between default and named exports in the source code.

Testing Constraints

In environments where production credentials are omitted to prevent security leaks, developers often implement conditional imports or mock services. If the module resolution fails during this switch, React triggers a specific warning during the render cycle.

The uncertainty lies in whether this behavior is a result of the test runner's module caching or a failure in the conditional logic used to swap real services for mocks based on process.env variables.

• Does the React.createElement invalid type error consistently trigger when a component is imported via a default import but exported as a named constant?
• How does the React renderer differentiate between a missing environment variable and a failed module export when triggering this warning?