Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Next.js 15 migration + next.js 15 static first mdx tutorial #80

Merged
merged 363 commits into from
Jan 1, 2025
Merged

Conversation

chrisweb
Copy link
Owner

@chrisweb chrisweb commented Jan 1, 2025

  • Next.js 15 / React 19 / ESLint 9 flat config migration
  • next.js 15 static first mdx tutorial (updated version of my previous nextjs 14 mdx tutorial, lots of changes:
    • tips on using the new typescript nextjs config (next.config.ts)
    • tips for when using turbopack and / or the mdx rust compiler (mdxjs-rs / mdxRs) when using mdx (rehype / remark) plugins
    • migrated from ESLint 8 to 9 and added chapter about creating a custom flat config, also added tips about using a typescript eslint config file (eslint.config.ts by using the new experimental unstable_ts_config flag)
    • migrated components to React 19 (update use of refs, ...)
    • improved opengraph image and dynamic sitemap scripts
    • adjustements due to updates in tools like CNA and the sentry wizard
  • the animation is less shiny than before, as currently the bloom filter is disabled, waiting for the react processing PR #302 to get merged

…e hook inside of the component, makes understanding it easier
…es next/link, styling it and adding a custom font using next/font
…ing to next.js 15, the second one is a disclaimer about things which won't work, to make sure that everyone knows right away what to expect
… not the "-save" flag as it will replace the tags with strict versions (btw when npm does this it forgets to make the changes in the overrides, causing installs to fail: EOVERRIDE)
Copy link

vercel bot commented Jan 1, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
chris-lu ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 1, 2025 1:56pm

@chrisweb chrisweb self-assigned this Jan 1, 2025
@chrisweb chrisweb requested a review from Copilot January 1, 2025 14:07

Choose a reason for hiding this comment

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

Copilot reviewed 193 out of 208 changed files in this pull request and generated no comments.

Files not reviewed (15)
  • .editorconfig: Language not supported
  • .vscode/settings.json: Language not supported
  • app/about_me/page.mdx: Language not supported
  • app/games/page.mdx: Language not supported
  • app/global.css: Language not supported
  • app/lego/page.mdx: Language not supported
  • app/memes/page.mdx: Language not supported
  • .eslintrc.js: Evaluated as low risk
  • .no-dead-urls.remarkrc.mjs: Evaluated as low risk
  • .remarkrc.mjs: Evaluated as low risk
  • README.md: Evaluated as low risk
  • app/about_me/opengraph-image.tsx: Evaluated as low risk
  • app/error.tsx: Evaluated as low risk
  • app/manifest.ts: Evaluated as low risk
  • app/loading.tsx: Evaluated as low risk
Comments suppressed due to low confidence (2)

app/lego/opengraph-image.tsx:19

  • [nitpick] The function name 'Image' is too generic and ambiguous. It should be renamed back to 'OGImage' to clearly convey its purpose of generating an Open Graph image.
export default async function Image() {

app/memes/opengraph-image.tsx:19

  • [nitpick] The function name 'Image' is too generic. It should be renamed to something more descriptive like 'OGImage'.
export default async function Image() {
@chrisweb chrisweb merged commit e480e10 into main Jan 1, 2025
4 checks passed
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.

1 participant