undefinedNext Route Visualizer is designed to display the routes for the app directory of Next.js (starting at version 13) in a visual tree-like fashion.
This package aims to help developers better understand the routes in their Next.js app directory by providing a clear visual representation of the routes and their relationships.
This package can be useful if you are new to the app directory and need to visualize it.
You can install next-route-visualizer using npm:
npm install next-route-visualizer
Once you’ve installed the package, you can import the Visualizer component into any page of your Next.js version 13 app directory.
For ease of use just import it in the root page for instance:
import Visualizer from 'next-route-visualizer';
export default function Home() {
return (
<Visualizer />
)
}
That’s it! The Visualizer component will render a tree chart that displays the routes of your Next.js app directory.
| Prop name | Type | Description |
|---|---|---|
| path | String or undefined | Path to the starting route (relative to the app directory). |
| baseURL | String or undefined | Base URL of your project. |
The below example shows how to use the path and baseURL parameters.
import Visualizer from 'next-route-visualizer';
export default function Home() {
return (
<Visualizer path="blog" baseURL="https://example.com" />
)
}
Only the sub-routes of blog (blog included) will be displayed on the chart. This assumes that blog is a direct sub-route of the app root (i.e ./app/blog in your file system).
Under the hood, next-route-visualizer utilizes ReactFlow to build the chart.
In order for the component to work properly, the routes need to be retrievef server side, and rendered on the client using ReactFlow.
For that reason, you must refresh the page to see any changes that you applied to your routes, for them to take effect on the chart.
This is a side project and I do not intend to maintain this component or resolve any issues in the future. The code is definitely a mess and I was too lazy to provide testing for it. I may be open to make a few changes if I feel like it.
On that note, please feel free to use and make any changes that you wish to include.
Note: I didn’t use tailwind or any other packages for the styles.
Next Router Visualizer is ISC licensed.
We use cookies
We use cookies to analyze traffic and improve your experience. You can accept or reject analytics cookies.