Repository navigation
[Snyk] Security upgrade @nrwl/next from 15.3.3 to 15.8.0 - #7
Merged
Merged
Conversation
….json & packages/nx/src/plugins/js/lock-file/__fixtures__/nextjs/package-lock.json to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-SEMVER-3247795
SherfeyInv
pushed a commit
that referenced
this pull request
May 7, 2026
## Current Behavior Searching for `nx.json` on nx.dev/docs does not surface the actual nx.json reference page in the top results. The `.NET Plugin for Nx` and other technology introduction pages rank higher because they have `weight: 5` in frontmatter, which inflates their body text scoring via Pagefind's `data-pagefind-weight` attribute (~25x impact via quadratic scaling). The same issue affects `project.json`, `inputs`, and other reference pages. ## Expected Behavior Reference pages whose title exactly matches the search query should rank first or near the top. Technology introduction pages should still be discoverable for their framework name but should not outrank reference pages for terms they merely mention in body text. **After this change:** - `nx.json` → "nx.json Reference" is `#1` (was `#7+`) - `project.json` → "Project Configuration" is `#1` - `angular` → "Angular Plugin for Nx" is `#1` (preserved) - `nest` → "Nest.js Plugin for Nx" is `#1` (preserved) - `react` → "React Plugin for Nx" is `#2` (React Native `#1` — valid match) **Changes:** - Reduce `weight` on 35 technology introduction pages from `5` → `2` to reduce body text inflation while keeping a modest boost - Reduce `weight` on adding-to-monorepo guide from `6.4` → `2` - Adjust Pagefind ranking params: `termFrequency: 0.75 → 0.65`, `pageLength: 0.5 → 0.3` to reduce the penalty on long reference pages ## Related Issue(s) Fixes DOC-475 Co-authored-by: Claude Opus 4.6 (1M context) <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
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.
This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
packages/nx/src/plugins/js/lock-file/__fixtures__/nextjs/package.jsonpackages/nx/src/plugins/js/lock-file/__fixtures__/nextjs/package-lock.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-SEMVER-3247795
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)