Fix misspelled moduleNameMapper key in jest.config.js#2
Closed
ruanbarroso wants to merge 1 commit into
Closed
Conversation
The custom Jest config used `moduleNameMapping`, which is not a valid Jest option, producing on every run: Validation Warning: Unknown option "moduleNameMapping" was found. This means your test cases might not behave as expected. The hand-written `^@/(.*)$` -> `<rootDir>/src/$1` mapping was silently ignored; the `@/` alias only resolved because next/jest injects its own moduleNameMapper derived from tsconfig paths. Renaming the key to the correct `moduleNameMapper` makes the entry valid and lets it merge with next/jest's generated mapper. Verified: `npm test` runs with no validation warning and all tests pass. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
jest.config.jsdefined the module alias under the keymoduleNameMapping, which is not a valid Jest option. On every test run Jest printed:Because the key was invalid, the hand-written mapping was silently dropped:
The
@/import alias kept working only by accident —next/jestinjects its ownmoduleNameMapperderived fromtsconfigpaths, so the dead entry was never actually needed.This PR renames the key to the correct
moduleNameMapper, so the entry is valid and merges with the mappernext/jestgenerates.Verification
npm testnow runs with no validation warning.Test Suites: 1 passed,Tests: 3 passed).🤖 Generated with Claude Code