Fix broken link to Next.js base path configuration #7419
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Hi @amarachiugwu! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
Size changes📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
3 participants
This pull request updates the React documentation in the "Add React to an Existing Project" section. Specifically, it fixes the broken link to the Next.js documentation on configuring a base path. The original link pointed to an outdated or incorrect URL, which could cause confusion for readers trying to implement a React application for a specific subroute, such as /some-app, using Next.js.
The updated link now directs users to the correct Next.js documentation page that explains how to configure a base path in a Next.js application.