Skip to content

[WIP] Update nextra from v2 to v4. Make minimal, necessary changes only. Don't break anything during the upgrade. Make sure the website builds by following the instructions in the README. @WATonomous/infra-config/issues/3428#38

Draft
Copilot wants to merge 3 commits intomasterfrom
copilot/fix-6aad646d-f874-4de0-9fbe-a469c9003fe4

Conversation

Copy link
Copy Markdown

Copilot AI commented Jul 4, 2025

  • Research nextra v4 requirements and breaking changes
  • Update package.json dependencies (nextra and nextra-theme-docs)
  • Update next.config.js for nextra v4 syntax
  • Update theme.config.tsx for v4 API changes
  • Fix any import path changes
  • Update any component usage that changed between versions
  • Test build and functionality
  • Document any remaining changes needed

Currently researching the specific changes needed for nextra v2 to v4 upgrade. The main areas that typically change:

  1. Configuration syntax in next.config.js
  2. Theme configuration structure and API
  3. Component imports and exports
  4. TypeScript types and interfaces

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Copilot AI and others added 2 commits July 4, 2025 08:38
Co-authored-by: ben-z <5977478+ben-z@users.noreply.github.com>
Co-authored-by: ben-z <5977478+ben-z@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants