@ijjk I can't edit labels myself. This PR is not about documentation (though I added some documentation to reflect the code change). It is about changing Next.js route.ts type definition to allow custom exports. Which is not currently possible.

Also the discussion (#55140) hasn't been picked up by anybody, do you know if I could mention someone who could be interested in having a look at my proposal ?

Are there any updates on this? I'm trying to colocate OpenAPI docs with the route implementation and this would be really handy.

Allow CI Workflow Run

• approve CI run for commit: f17b419

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

Are there any updates on this? I'm trying to colocate OpenAPI docs with the route implementation and this would be really handy.

@jens-ox Nothing new unfortunately, it's a bit sad to let small PRs like this one fade away. It has been a year.
Colocation in API routes seems pretty unharmful and could enable a lot of nice features (especially around type inference imo). I wonder if there is more to it, or if it is simply a lack of visibility.

I rebased the PR to have a clean commit that can be merged into the current canary branch, let's see if it can make it to Next.js 15
@leerob you looked at it at least once a while back, maybe you can give us some feedback ? that would be great

@theo-lubert

Some cases require to export some info: data, configs, types for the client, etc...

Wouldn't you want these /lib type of logic in a separate directory?

could enable a lot of nice features (especially around type inference imo).

Is it possible to elaborate on this (versus having like a separate types.ts file)?

Next.js currently forces us to create separate files

Is the issue because the thought is you can't export multiple methods in a Route Handler?

@samcx

You could build a custom wrapper in /lib. But you wouldn't write the actual route specific logic outside of the route.ts file.

That wrapper could expose:

• inferred types from the methods
• callable local js functions, for use from other routes, RSC, jobs, etc
• OpenAPI data (as @jens-ox mentionned)
• metadata
• ... probably a lot more

There is currently no way to do that from route.ts, where the actual info is.

const apiRoute = customCRUD({ model: UserModel })
// or maybe
const apiRoute = customCRUD({
    create: {
        input: z.object({
            title: z.string(),
        }),
        handler: ({ title }) => return { title }
    },
})

// This works as intended
export { GET, POST } = apiRoute

// This is not allowed, even though `apiRoute` is what contains the actual info, inside `route.ts`
export { _createInputType, _openAPISchema, /* etc */ } = apiRoute

• An other example for this is a lib I started working on last year (@trestjs/react-query) that exposes reactQuery hooks based on the types inferred form the routes. There is no supported path to make that work in the current Next.js state

Hi @samcx @leerob what can we do to make this happen ? or at least move in any direction ? A year is a long time. It really is a small change. Thx a lot