Nextjs 15, Tailwind 4 and ShadCN Integrated

[vipertecpro]

Please check this out, if this requires any other critical changes, i did best of my knowledge to upgrade this.

[Willem-Jaap]

Good update, this probably won't get merged as the team is working on new starterkits, see: #58 (comment) so I think it's best you maintain your own starter kit until then

Other than that I have the following suggestions:

• Remove .idea/ from source control
• Remove next-env.d.ts from source control, should be generated using dev/build
• Make sure all filenames use the same casing

Not related to this PR exactly but please implement some form of auth check using middleware: https://nextjs.org/docs/app/building-your-application/authentication#session-management.

[vipertecpro]

Thanks a lot for the great suggestions, @Willem-Jaap ! It's really helpful to get insights from someone other than just myself.

I hope you don’t mind me asking, but if you ever have time, I'd really appreciate it if you could keep an eye on my repo and share any suggestions. I'm aiming to improve my approach more realistically.

I implemented these changes within 8-9 hours while testing each build to ensure it aligns with a production environment.

Also, I’d love your input on the best approach for this:
How should Laravel + React + DataTables be integrated using [ShadCn Datatables](https://ui.shadcn.com/docs/components/data-table)? Or should we manually structure and update each component with [ShadCn Table](https://ui.shadcn.com/docs/components/table)? Since a proper table setup is a fundamental requirement for any starter kit, I’d like to ensure it's done efficiently.

Regarding server-side pagination, search, and filtering:

• The query parameters (?page=1&sortField=name&sortOrder=asc&search=Hello) shouldn't be visible anywhere in the client right, correct?
• However, the search input and sort button should trigger events on the client component, sending values to the server component for data fetching—yet the data remains visible. Is that expected behavior?

Would Server Actions be the ideal solution here? [Next.js Server Actions](https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations) seem like a potential approach.

Looking forward to your thoughts! 🚀

[Willem-Jaap]

Regarding the query parameters, they actually should be visible. This ensures that the state is preserved when reloading the page or sharing the URL. Otherwise, users might lose their search, sorting, or pagination settings when navigating away and back.

A great library for managing this in React is nuqs. We use this strategy heavily internally:

• We fetch data using SWR on the client. (prefetching serverside and passing to SWR on the client is also possible but not required for our usecase.
• We use nuqs in shallow mode to update the search params without causing a full page reload.

This approach makes everything feel smooth while still keeping the URL in sync with the app state. You could also use a more server driven approach using serverside search params and fetching serverside. I wouldn't use server actions for this as it is not a POST or PUT, rather just update searchParams which refreshes page using updated search params.

If you have more questions we should probably move out of this PR, feel free to reach me on x