spread-real-module-exports-as-base-of-every-mock-module-return-o

Node.js mock.module tests fail when default mock return objects exclude real module exports. Spreading real module exports as the base of every mock return object aligns mock behavior with actual interfaces and restores missing properties.

To spread real module exports in a mock.module return object, apply the spread operator to the real module's exports as the base before overriding specific properties, ensuring the mock maintains the actual module interface.

The best way to enforce consistent mock.module patterns is to use automated grep checks that validate every mock.module return object includes the required real module spread, catching missing patterns early in development.

Yes, you can use this pattern for Node.js integration tests. Spreading real module exports as the base of mock.module return objects ensures mock behavior reflects actual module interfaces across both unit and integration test scenarios.

You need to spread real exports in Node.js mock modules whenever you use the built-in mock.module functionality to create mocks, as default return objects lack real exports and cause incorrect mock behavior.