Best Practice for Directory Structure For File-based?

I'm new to using Routing libraries of any kind, and I'd like to come up with a folder structure in my project that makes the most sense.

I'm using file-based routing. My pages will have multiple components in them, of course, and I'd like to keep those components close to the actual page component I'm developing. Putting the Page component and its child components under the

routes

routes

directory won't work well since Tanstack Router will create a route structure. This is what I'm working with now:

├── pages
│   └── initialVerification
│       └── InitialVerificationPage.tsx
├── routeTree.gen.ts
├── routes
│   ├── __root.tsx
│   ├── _compose.compose.initialVerification.tsx
│   ├── _compose.tsx
│   ├── about.lazy.tsx
│   └── index.tsx

├── pages
│   └── initialVerification
│       └── InitialVerificationPage.tsx
├── routeTree.gen.ts
├── routes
│   ├── __root.tsx
│   ├── _compose.compose.initialVerification.tsx
│   ├── _compose.tsx
│   ├── about.lazy.tsx
│   └── index.tsx

I'll have a

pages

pages

directory that mirrors the

routes

routes

directory. Is this overkill? Is there some better way to do this?

What are most folks doing when it comes to organizing their project?

TanStack•16mo ago•

1 reply

significant-gray

Best Practice for Directory Structure For File-based?

routes

routes

directory won't work well since Tanstack Router will create a route structure. This is what I'm working with now:

├── pages
│   └── initialVerification
│       └── InitialVerificationPage.tsx
├── routeTree.gen.ts
├── routes
│   ├── __root.tsx
│   ├── _compose.compose.initialVerification.tsx
│   ├── _compose.tsx
│   ├── about.lazy.tsx
│   └── index.tsx

├── pages
│   └── initialVerification
│       └── InitialVerificationPage.tsx
├── routeTree.gen.ts
├── routes
│   ├── __root.tsx
│   ├── _compose.compose.initialVerification.tsx
│   ├── _compose.tsx
│   ├── about.lazy.tsx
│   └── index.tsx

I'll have a

pages

pages

directory that mirrors the

routes

routes

directory. Is this overkill? Is there some better way to do this?

What are most folks doing when it comes to organizing their project?

Best Practice for Directory Structure For File-based?

Similar Threads

Best Practice for Directory Structure For File-based?

Similar Threads

Similar Threads

Similar Threads