Skip to content

Update npm runtime dependencies in the website - #10311

Merged
glen-84 merged 3 commits into
mainfrom
gai/website-npm-runtime-dependencies
Aug 28, 2026
Merged

glen-84 merged 3 commits into
mainfrom
gai/website-npm-runtime-dependencies

Conversation

@glen-84

@glen-84 glen-84 commented Aug 28, 2026

Copy link
Copy Markdown
Member

Summary

  • Moves every age-gated (7+ days) runtime dependency of the website forward: next, @next/mdx, and eslint-config-next to 16.3.2 (clearing nine next advisories and, transitively, the postcss and nanoid ones), js-yaml to 5.3.0, sharp to 0.35.3, react and react-dom to 19.2.8, and @fortawesome/*, @xyflow/react, shiki, styled-components, @docsearch/* (4.7.0), and motion (13.1.1) to their current releases.
  • Removes @next/third-parties (unused since the GTM loader moved to next/script) and @types/js-yaml (js-yaml 5 ships its own types), moves @types/mdx to devDependencies, and switches the contact form's thank-you redirect to useRouter().push as the extended no-location-assign-relative-destination rule asks.
  • Adds website/yarn.lock to the optimized-images cache key so a sharp bump re-encodes the AVIF/WebP set instead of reusing cached output.

Held back: @docsearch/* 5.x (the Ask AI release, six new runtime dependencies) and elkjs 0.12 (an entry that only satisfies the Mocha visualizer's peer range).

Test plan

  • yarn install, tsc --noEmit, yarn lint, and yarn build after each bump; yarn optimize-images for the sharp bump; yarn test:visual for shiki and motion (all CodeBlock and motion-component baselines pass).
  • Static build served locally and compared against production in a headless browser: the Fusion and Mocha topology diagrams, TOC anchor scrolling and soft navigation, the OG share card (byte-identical), the Nitro download widget (js-yaml 5 parsing the CDN manifest), and the Nitro product page.
  • Left for the preview deployment: the DocSearch modal, since the Algolia credentials exist only in CI.

Copilot AI lite review requested due to automatic review settings August 28, 2026 14:29

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the website’s runtime dependency set (Next.js/React ecosystem and supporting libraries) and applies small code/workflow adjustments needed to align with those upgrades and CI caching behavior.

Changes:

  • Bumps website runtime dependencies (Next.js, React, sharp, js-yaml, shiki, styled-components, DocSearch, FontAwesome, xyflow, motion) and refreshes yarn.lock.
  • Removes unused/obsolete packages (@next/third-parties, @types/js-yaml) and moves @types/mdx to devDependencies.
  • Switches the contact form thank-you navigation to useRouter().push and updates the optimized-images cache key to account for dependency changes.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated no comments.

Show a summary per file
File Description
website/yarn.lock Lockfile refresh to reflect updated dependency graph and removals.
website/src/helpers/buildContentTree.ts Updates js-yaml import style to use load directly.
website/package.json Bumps/cleans dependency declarations and reclassifies types packages.
website/app/(content)/services/support/contact/ContactForm.tsx Replaces window.location.assign with Next.js router navigation for the thank-you redirect.
.github/workflows/publish-website.yml Adjusts optimized-images cache key so dependency bumps (notably sharp) invalidate cached encodes.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@glen-84
glen-84 merged commit 389a401 into main Aug 28, 2026
293 of 295 checks passed
@glen-84
glen-84 deleted the gai/website-npm-runtime-dependencies branch August 28, 2026 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants