Repository navigation
docs: state NestJS 9-12 compatibility - #129
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The docs never named the supported NestJS range, so a visitor on NestJS 12 had to read package.json to learn it is supported. Add the range to the installation page and the landing FAQ, which also feeds the FAQPage JSON-LD search results.
KevinEdry
force-pushed
the
docs/nestjs-12-compat
branch
from
November 2, 2026 22:32
75f916a to
755c747
Compare
KevinEdry
enabled auto-merge (rebase)
November 2, 2026 22:32
This branch was successfully deployed
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
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.
#122 widened the peer ranges to NestJS 12, but the docs never named the supported NestJS range anywhere — a visitor on NestJS 12 had to read
package.jsonto learn it works.This states the range in the two places people look: a compatibility line on the installation page, and the landing FAQ's versions question, which also feeds the
FAQPageJSON-LD that search engines surface for queries like "nestjs 12 trpc".No other page pinned a version, so nothing else needed correcting.