Exporting a router file is not working about tinyhttp HOT 7 CLOSED

In summary, @tinyhttp/router is more like an internal package. You should use subapps. For example

import { App } from "@tinyhttp/app"

const subApp = new App()
const app = new App()

subApp.post("/auth", handler)

app.use(subApp)

from tinyhttp.

Hi there. Thanks for posting the issue. Could you please post the import and subsequent use of authRoutes?

from tinyhttp.

The authRoutes is literally the imported router file which I described its contents, so I import it like usual, import router as authRoutes from "./authRoutes.js"

from tinyhttp.

The authRoutes is literally the imported router file which I described its contents, so I import it like usual, import router as authRoutes from "./authRoutes.js"

@talentlessguy, replied to a similar issue. See #400 (comment)

from tinyhttp.

Thanks so much @aarontravass! I see.

Was it designed to be that way? What would be the advantages of using this style of "subapps" over creating Router objects and integrating(.use) them in the main app, like I did?

Also, what is the point of @tinyhttp/router then? What would be the use case for this feature?

Adding a few more context to this internal package on its README page would probably help others in the future who would end up in the same situation as me or this person who you mentioned.

from tinyhttp.

Was it designed to be that way?

Yes, I believe so.

What would be the advantages of using this style of "subapps" over creating Router objects and integrating(.use) them in the main app, like I did?

The router is just a bare-bones module and by itself has little to no use. Subapps are regular apps which can be nested and hence you have full control of each nested app which makes them way more powerful. This control is in the form of options/settings. The following are the ones you can set

In contrast, the router gives no such flexibility.

Also, what is the point of @tinyhttp/router then?

The router just holds the middleware. Each handler or subapp you pass becomes the middleware for the main app/sub app and this is held in the router.

What would be the use case for this feature?

I am not sure about this.

Adding a few more context to this internal package on its README page would probably help others in the future who would end up in the same situation as me or this person who you mentioned.

Yes, I think this would be a good idea.

from tinyhttp.

As was mentioned before, @tinyhttp/router is an internal package. I'm sorry for confusion, I'll add a "this is an internal package and is not meant to be used directly" to README.

Router's purpose is to move off middleware management to a separate utility class, router. You can't use it together with App unless you do some customization on top of it.

from tinyhttp.