Added @types/jest in installtion commands. #78090
Merged
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.
For Contributors
Improving Documentation
pnpm prettier-fix
to fix formatting issues before opening the PR.Adding or Updating Examples
pnpm build && pnpm lint
.See: Linting Docs
Fixing a Bug
fixes #number
.Reference: Error Links Guide
Adding a Feature
(Ensure there's an approved discussion: Submit Idea)
fixes #number
.See: e2e Testing Guide
For Maintainers
Fixes NEXT-xxx
) and GitHub issues.What?
Updated documentation and installation instructions to include
@types/jest
.Why?
When setting up Jest in a TypeScript project, omitting
@types/jest
causes TypeScript to fall back tonode:test
, leading to incorrect module resolution and runtime errors. Including@types/jest
resolves this and ensures a smooth development experience.How?
Added
@types/jest
to the recommended install commands wherever applicable, ensuring consistent and error-free setup for users following the docs.Closes
NEXT-
Fixes
#