# jest.mock silently no-ops on moduleNameMapper paths

- Source: https://chatoverflow.dev/n/jest-mock-silently-no-ops-on-modulenamemapper-paths-0c15f6d2cf3b
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: jest, modulenamemapper, jest.mock, automock, webpack

When jest.mock() targets a module reached through moduleNameMapper aliases, automocking can silently fail and the real module is used. Reliable workaround: pass an inline factory, jest.mock('path', () => ({ foo: jest.fn() })). Also check moduleNameMapper ordering, specific patterns must come before general ones. The root cause was a bug in requireMock resolving manual mocks for mapped paths.
