You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently rely on Shiki version 1 for syntax highlighting in our Next.js starter project. With the release of Shiki version 3—which brings improvements in performance, theme handling, and API consistency—it’s time to upgrade our integration.
Migration Goals:
Upgrade Dependency: Update the project’s package.json to reference Shiki v3.
API Updates: Refactor our codebase to accommodate breaking changes and new API patterns introduced in v3.
Validate that the migration script covers all required changes from the v1 API.
Code Refactoring:
Review the migration output for any manual adjustments needed.
Update any custom integrations or overrides to work with the new API.
Testing:
Execute the existing test suite to ensure nothing breaks.
Manually verify syntax highlighting in both development and production builds.
Check for any visual discrepancies or performance regressions.
Documentation:
Update README and any related docs with the new installation and usage instructions for Shiki v3.
Add notes on migration steps for future reference.
Additional Context:
The automated migration instructions from the Shiki team provide a clear path for updating from earlier versions. This migration is critical to take advantage of the latest features and maintain compatibility with modern Next.js setups.
Let’s prioritize this update to ensure our starter project remains up to date and fully leverages the improvements in Shiki v3.
The text was updated successfully, but these errors were encountered:
Description:
We currently rely on Shiki version 1 for syntax highlighting in our Next.js starter project. With the release of Shiki version 3—which brings improvements in performance, theme handling, and API consistency—it’s time to upgrade our integration.
Migration Goals:
Tasks:
Update Package Dependency:
package.json
.Run Automated Migration Script:
Code Refactoring:
Testing:
Documentation:
Additional Context:
The automated migration instructions from the Shiki team provide a clear path for updating from earlier versions. This migration is critical to take advantage of the latest features and maintain compatibility with modern Next.js setups.
Let’s prioritize this update to ensure our starter project remains up to date and fully leverages the improvements in Shiki v3.
The text was updated successfully, but these errors were encountered: