How to structure an Inertia.js project with separate directories for different UI libraries (shadcn-ui for client, Ant Design for admin)

[only-issues]

Hello everyone,

I'm new to Inertia.js and currently working on a project where I need to use different UI libraries for different parts of the application:

• Client-side: Using shadcn-ui
• Admin panel: Using Ant Design (antd)

I'd like to structure my project with separate directories for each part to better manage the different UI libraries:

js/
├── admin/
│   ├── app.tsx
│   ├── components/
│   └── pages/
└── client/
    ├── app.tsx
    ├── components/
    └── pages/

Since these two areas use completely different UI libraries, I want to keep them separate for better organization and to avoid conflicts.

Is this possible with Inertia.js? If so, how would I configure it to support this structure? Would I need multiple entry points in my build configuration?

I'm particularly concerned about:

1. How to set up the routing for both client and admin areas
2. How to configure vite to handle multiple entry points
3. Whether there are any best practices for this kind of structure in Inertia.js projects

Any guidance or examples would be greatly appreciated!

Thank you.

[vitalijalbu]

Wanted the same months ago, basically u will need to have 2 views app.blade.php and some little code inside a middleware, meaning it will tell you which url (does it start with /admin or not)...