Announcing shadcn-admin v1: What's Coming Next!

[satnaing]

Hello, everyone! 👋

First of all, I want to extend a huge thank you to everyone who has shown interest in shadcn-admin. 🙌

As some of you may know, shadcn-admin is currently in its beta phase, and I'm excited to share some major updates that are on the way. With the next release, I’m planning a significant version bump to bring even more features, stability, and improvements. Here’s a sneak peek of what you can expect:

✨ What's Coming Next

• Migrating from React Router to TanStack Router: This change will bring better DX and more advanced routing capabilities, making your experience even smoother.
• Updating the folder structure to feature-based approach: The entire folder structure will be updated to a feature-based organization for better scalability and maintainability.
• Replacing the custom sidebar with Shadcn UI's native sidebar: To enhance consistency and usability, the new sidebar will leverage Shadcn UI's native components, offering a more seamless design.
• Upgrading ESLint from v8 to the Latest v9 Flat Config: Expect improved linting capabilities with the latest ESLint updates, helping maintain clean, efficient, and error-free code.

These changes are part of my ongoing effort to make shadcn-admin a robust and scalable admin dashboard solution for everyone.

Stay tuned for more updates, and as always, your feedback is welcome! 🚀💙

Best,
Sat Naing

[devshinthant]

Excellent Idea!! 🚀

[zhuxining]

why not react router 7?

[satnaing]

I've used both react-router and tanstack-router, and don't get me wrong_ react-router is a fantastic routing library. However, the developer experience (DX) of integrating tanstack-router into my React projects is simply better and more intuitive. This might be subjective, of course, but the TanStack ecosystem, combined with better type safety and an improved DX, is arguably superior.

Additionally, this project uses shadcn-ui and shadcn-ui itself is leveraging tanstack-table for its table UI/layouts. So, it just makes sense to use tanstack-router for routing as well.

Also, since this is a SPA project, we'll eventually have to deal with some sort of client-side fetching and async state management. I would choose tanstack-query for that too. So, we can have the seamless exp by usingtanstack-query + tanstack-router + tanstack-table in one project.

[satnaing]

PR #52