@eliyya/type-routes NPM

type-routes

Type your routes to avoid 404 redirects or callbacks.

Just only install with

npm i @eliyya/type-routes

Configure your next.config.mjs

import { withTypeRoute } from '@eliyya/type-routes/next'

export default withTypeRoute({
    /* config options here */
})

Or run the cli to update your app's paths manually if you don't want to modify your next.config.mjs.

npx type-routes

And use in your application

import { app } from '@eliyya/type-routes'

export async function AdminPage() {
    const user = await getUser()

    if (!user) redirect(app.login())
    if (!user.admin) redirect(app())

    const adminInfo = await api(app.api.adminInfo(), { id: user.id })

    return (
        <>
            <nav>
                <Link href={app.admin.panel()}></Link>
                <Link href={app.admin.watcher()}></Link>
            </nav>
            <Dashboard info={adminInfo} />
        </>
    )
}

if the path is only a directory that contains more directories inside, will return an object with the directories that are found inside as properties with their respective type
Example: src/app/user/settings/ will be converted to app.user and return { settings: ... }
If the path contains a page.js file or route.js file, it can be run as a function to return the string corresponding to the path
Example: src/app/user/page.js will be converted to app.user() and return '/user/'
If it is a dynamic route marked by the [dirname] convention, it will be renamed to $dirname and the function will receive the parameters, this applies to your paths within it.
Example:src/app/user/[id]/[option]/page.js will be converted to app.user.$id.$option('123', 'abc') and return '/user/123/abc/'
if the path is a catch-all segment marked by the convention [...dirname], it will be similar to a Dynamic Path, but it will be renamed to $$dirname
Example:src/app/user/[...rest]/page.js will be converted to app.user.$$rest('123', 'abc') and return '/user/123/abc/'

Motivation

Creating new routes with a file-based router is so easy that sometimes we forget to update all the references in our code when a route is removed or changed.

Nextjs is taking action with the experimental typedRoutes option, however, this only works when used in Link tags, so there can be errors in runtime when using a redirect or even in references within our code.

This package solves it in a magic and comfortable way bringing the routes as safe type functions to be able to provoke an error in compilation and to avoid disasters with a simple way to use it without so much configuration.