Skip to content

Fix broken links to the React 19 Upgrade Guide - #8601

Open
see-stack wants to merge 9 commits into
reactjs:mainfrom
see-stack:fix-renamed-blog-links
Open

Fix broken links to the React 19 Upgrade Guide#8601
see-stack wants to merge 9 commits into
reactjs:mainfrom
see-stack:fix-renamed-blog-links

Conversation

@see-stack

Copy link
Copy Markdown
Contributor

Three links still used the old /blog/2024/04/25/react-19 path, which 404s since the page was renamed to react-19-upgrade-guide. Updated them to the current path.

@github-actions

Copy link
Copy Markdown

Size changes

Details

📦 Next.js Bundle Analysis for react-dev

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

@deepusnath

Copy link
Copy Markdown

These links aren't currently broken — vercel.json (L248) permanently redirects /blog/2024/04/25/react-19 → /blog/2024/12/05/react-19, and the fragment is preserved, so they land on the right headings today.

The new target is the problem: react-19-upgrade-guide.md doesn't define {/error-handling/} or {/ref-as-a-prop/} — those headings live in blog/2024/12/05/react-19.md (L727 and L396). So after this change the pages load but drop the reader at the top of the wrong post, which a link checker won't flag.

If the goal is to skip the redirect hop, the repo already has a convention for that — useImperativeHandle.md:49 links straight to /blog/2024/12/05/react-19#ref-as-a-prop. Retargeting to that path instead would work.

@see-stack

see-stack commented Aug 22, 2026

Copy link
Copy Markdown
Contributor Author

Thanks for catching this!