219 comments found.
The codebase is unnecessarily complex and difficult to follow. Its structure and organization are far from what most developers would consider intuitive, making it challenging even for experienced programmers to navigate. I would only consider it suitable for a very small group of experts, and even seasoned professionals generally prefer solutions that are simpler and easier to maintain. Overall, I don’t see any significant advantage in adopting this approach and would not recommend it.
Thank you for your feedback.
This theme has been successfully used in multiple SaaS products and has sold numerous licenses across different use cases which reflects its real-world reliability and adoption.
The architecture is intentionally modular and built for large, scalable applications. To get the most out of it, familiarity with the underlying architectural patterns is recommended as with any production-grade codebase.
If this theme doesn’t match your project’s needs, you’re welcome to submit a refund request and we’ll be happy to assist.
Thank you for your response.
I understand that the theme is designed for large-scale applications and may suit certain projects. However, after reviewing the codebase in depth, I found that its architecture and level of complexity do not align with my requirements and preferred development workflow.
Maintainability and ease of understanding are important factors for my team, and unfortunately this product does not meet those expectations for our use case. Since the product is not suitable for our needs, I would like to request a refund in accordance with your refund policy.
Thank you for your assistance, and I appreciate your understanding.
Hello,
I am evaluating your theme for use in a commercial SaaS application and would like to clarify the licensing requirements.
Our application is a multi-tenant SaaS platform for VFX project management. Multiple customers (tenants) access the same hosted application through subscription plans. The theme is used only as the user interface layer and is integrated into our application.
Key details:
- Single hosted SaaS application.
- Multi-tenant architecture (all customers use the same platform).
- Customers pay a subscription fee to access the service.
- The theme source code, assets, and templates are not redistributed, resold, or provided to customers.
- Customers access the application only through their web browser.
- We do not provide separate copies of the application to each customer.
Could you please confirm:
1. Whether a single Extended License is sufficient for this use case. 2. Whether any additional licenses are required because the application is multi-tenant. 3. Whether separate licenses would be needed if we later offer dedicated or white-labeled deployments for individual customers.
Thank you for your clarification.
Thank you for reaching out and providing such clear details about your architecture.
1. Yes, a single Extended License is exactly what you need for your urrent setup. 2. 3. No, no additional licenses are required for multi-tenancy.
Thanks
hello, can reinv me for github? https://github.com/AzazelDaniel
Kindly provide the Figma file for this design for making the prototype.
Hi, currently we dont have fima file
When selecting items in the table, the highlight overlay gradually becomes more opaque and starts overlapping the buttons (Cancel, Delete, etc.).
HI, we will check and fix it asap, thanks
Hello sir. Is there any figma file? i need that for designing my own website
thanks
Hi, currently we dont have fima file
I see, thank you. But in the future hopefully figma provided 
I want to develop with Laravel. Do you have the HTML, CSS, and JavaScript files?
Hi, This is React template, for HTML/Laravel, you can check https://themeforest.net/item/lineone-multipurpose-admin-and-webapp-ui-kit-based-on-tailwind-css/38247812
Best Regards
Request for Technical Architecture & Library Details – React Template
Hello,
I hope you’re doing well.
I am planning to build a large-scale, production-grade application using React, and I am currently evaluating templates on ThemeForest for long-term use. Your template stood out to me, and I am very interested in purchasing it.
Before proceeding, I wanted to understand a bit more about the technical foundation to ensure it aligns with my project requirements. Specifically, I would appreciate it if you could share details on:
Overall frontend architecture and folder structure
State management approach (e.g., Redux, Zustand, Context API, etc.)
Routing strategy
Styling solution used (CSS modules, styled-components, Tailwind, etc.)
Major third-party libraries and their purpose
Scalability considerations and best practices followed
TypeScript usage (if applicable)
Testing setup (if included)
My goal is to choose a template that is maintainable, scalable, and suitable for enterprise-level development.
Thank you for your time and support. I look forward to your response and hopefully working with your template.
Best regards, Hiren
Hi Hiren,
Thank you for your message and for your interest in our React template, we’re glad it caught your attention.
We actively maintain and update the theme with long-term support, including compatibility updates and improvements over time.
Here are the technical details you requested:
Frontend architecture & folder structure: The project follows a modular and scalable folder structure. Each feature/module is organized separately, making it easy to add, modify, or remove modules as your application grows. Shared components, layouts, and utilities are clearly separated to support enterprise-level maintainability.
State management: We use the React Context API by default. This keeps the core lightweight and makes it easy to integrate any external state management library such as Redux, Zustand, or others if your project requires more advanced patterns.
Routing strategy: Routing is implemented using React Router.
Styling solution: We use Tailwind CSS for styling.
Third-party libraries: A curated set of commonly used and production-ready libraries is included for UI, forms, charts, and utilities. You can find the full and up-to-date list here: https://tailux.piniastudio.com/docs/attributions.
Scalability & best practices: The template is built with reusability and scalability in mind, including modular design, reusable UI components, separation of concerns, and configurable layouts.
TypeScript support: We provide two editions: TypeScript and JavaScript. You can choose the version that best fits your workflow and team requirements.
For more detailed documentation and structure overview, please see: https://tailux.piniastudio.com/docs/getting-started.
If you have any additional technical questions, I’ll be happy to clarify them.
Best regards
Nice Work
Hello Tailux Support Team,
I hope you’re doing well. I’m currently using the Tailux multi-select/autocomplete component in my project and have also built a custom personal component for comparison (screenshots attached). I wanted to ask if it would be possible for your team to either update the existing component or introduce a new variant with the following improvements: 1. Selected Items Count Display When multiple values are selected: Automatically calculate the total selected items Display the count (e.g., “3 selected”, “5 selected”) instead of, or in addition to, listing all selected values inside the input This would greatly improve readability when many items are selected. 2. Clear Search Input After Selection (UX Improvement) Currently, when I: Type a search term (e.g., “w”) Select an option from the dropdown The search text remains in the input, requiring the user to manually backspace and clear it before performing another search. This feels a bit unintuitive from a UX perspective. In my custom component, the search input automatically clears after selection, allowing users to continue searching immediately, which provides a smoother experience. It would be great if the Tailux component could: Automatically clear the search input after an item is selected Keep focus in the input for faster multi-selection Since I’ve purchased an additional support plan, I wanted to check if these enhancements are feasible or planned for a future update. Thank you for your time and support. I appreciate your work on Tailux and look forward to your guidance. Best regards, RS.
Hello RS,
Thank you for reaching out, and for the detailed explanation. We truly appreciate the time you took to share thoughtful feedback. There are not any screenshots, can you send your screenshots in piniahelp@gmail.com ?
Will I get lifetime updates with this theme?
Hi, Yes.
Hi Team, Can you please share UX design for this template
Hi, we dont have figma files.
Can I get figma along with the theme for mobile view?
Hi, we currently don’t have the Figma designs available. Best regards,
Where can I find the project figma? with the components?
Hi, we currently don’t have the Figma designs available. Best regards,
Hi! Is there a landing page that comes with this? I love the page at https://tailux-landing.vercel.app but I’m not able to find it in the demo app.
Hi! Thanks for your purchase and your comment.
The demo landing page is built with Next.js and React.js. It’s only meant to showcase Tailux features and isn’t part of the commercial package, so support for it isn’t included.
However, if you’d like access to the source code, just share your GitHub username and I’ll add you to the landing page demo repo
Best Regards
That would be amazing! Thanks! My GitHub username is primetheus
Invited
I recently purchased Tailux. I’m trying to compile the demo and starter with `npm run build`, but it’s generating errors and not completing the process in both JavaScript and TypeScript. Could you please help me with this?
papa@salmos:/workspace/tailux/ts/demo$ npm run dev
> react-tailux-ts-vite@1.3.2 dev > vite
0:08:23 [vite] (client) Re-optimizing dependencies because vite config has changed ^C papa@salmos:/workspace/tailux/ts/demo$ ls eslint.config.js node_modules package-lock.json public src tsconfig.json vercel.json index.html package.json prettier.config.js README.md tsconfig.app.json tsconfig.node.json vite.config.ts papa@salmos:/workspace/tailux/ts/demo$ npm run build
VITE v7.2.2 ready in 1463 ms➜ Local: http://localhost:5173/
➜ Network: use --host to expose
➜ press h + enter to show help> react-tailux-ts-vite@1.3.2 build > tsc -b && vite build
src/app/pages/dashboards/cms-analytics/PageViews/Statistics.tsx:34:9 – error TS2322: Type ‘Dispatch<SetStateAction<Page>>’ is not assignable to type ‘(value: unknown) => void’. Types of parameters ‘value’ and ‘value’ are incompatible. Type ‘unknown’ is not assignable to type ‘SetStateAction<Page>’.
34 onChange={setSelectedPage} ~~~~
node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
21 onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
~~~~
The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & { data: DataItem[]; placeholder?: string | undefined; label?: ReactNode; displayField?: string | undefined; error?: string | ... 1 more ... | undefined; ... 11 more ...; invalid?: boolean | undefined; } & Omit<...> & RefAttributes<...>'src/app/pages/forms/KYCForm/components/DocumentType.tsx:45:9 – error TS2322: Type ‘DocumentType | null’ is not assignable to type ‘DocumentType | undefined’. Type ‘null’ is not assignable to type ‘DocumentType | undefined’.
45 value={documentTypes.find((doc) => doc.key === value) || null} ~~~
node_modules/@headlessui/react/dist/components/radio-group/radio-group.d.ts:13:5
13 value?: TType;
~~~
The expected type comes from property 'value' which is declared here on type 'IntrinsicAttributes & CleanProps<"div", "value" | "disabled" | "form" | "defaultValue" | "onChange" | "name" | "by" | RadioGroupPropsWeControl> & OurProps<...> & { ...; } & { ...; } & { ...; }'src/app/pages/forms/autocomplete/Styled.tsx:32:9 – error TS2322: Type ‘Dispatch<SetStateAction<Person>>’ is not assignable to type ‘(value: unknown) => void’. Types of parameters ‘value’ and ‘value’ are incompatible. Type ‘unknown’ is not assignable to type ‘SetStateAction<Person>’.
32 onChange={setSelected} ~~~~
node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
21 onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
~~~~
The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & { data: DataItem[]; placeholder?: string | undefined; label?: ReactNode; displayField?: string | undefined; error?: string | ... 1 more ... | undefined; ... 11 more ...; invalid?: boolean | undefined; } & Omit<...> & RefAttributes<...>'src/app/pages/forms/autocomplete/StyledError.tsx:33:9 – error TS2322: Type ‘Dispatch<SetStateAction<Person[]>>’ is not assignable to type ‘(value: unknown) => void’. Types of parameters ‘value’ and ‘value’ are incompatible. Type ‘unknown’ is not assignable to type ‘SetStateAction<Person[]>’.
33 onChange={setSelected} ~~~~
node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
21 onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
~~~~
The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & { data: DataItem[]; placeholder?: string | undefined; label?: ReactNode; displayField?: string | undefined; error?: string | ... 1 more ... | undefined; ... 11 more ...; invalid?: boolean | undefined; } & Omit<...> & RefAttributes<...>'src/app/pages/forms/autocomplete/StyledHighlight.tsx:32:9 – error TS2322: Type ‘Dispatch<SetStateAction<Person[]>>’ is not assignable to type ‘(value: unknown) => void’. Types of parameters ‘value’ and ‘value’ are incompatible. Type ‘unknown’ is not assignable to type ‘SetStateAction<Person[]>’.
32 onChange={setSelected} ~~~~
node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
21 onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
~~~~
The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & { data: DataItem[]; placeholder?: string | undefined; label?: ReactNode; displayField?: string | undefined; error?: string | ... 1 more ... | undefined; ... 11 more ...; invalid?: boolean | undefined; } & Omit<...> & RefAttributes<...>'src/app/pages/forms/autocomplete/StyledMultiple.tsx:32:9 – error TS2322: Type ‘Dispatch<SetStateAction<Person[]>>’ is not assignable to type ‘(value: unknown) => void’. Types of parameters ‘value’ and ‘value’ are incompatible. Type ‘unknown’ is not assignable to type ‘SetStateAction<Person[]>’.
32 onChange={setSelected} ~~~~
node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
21 onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
~~~~
The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & { data: DataItem[]; placeholder?: string | undefined; label?: ReactNode; displayField?: string | undefined; error?: string | ... 1 more ... | undefined; ... 11 more ...; invalid?: boolean | undefined; } & Omit<...> & RefAttributes<...>'src/components/shared/table/FilterSelector.tsx:100:7 – error TS2322: Type ‘(list: FilterOption[]) => void’ is not assignable to type ‘(value: (FilterOption | undefined)[]) => void’. Types of parameters ‘list’ and ‘value’ are incompatible. Type ‘(FilterOption | undefined)[]’ is not assignable to type ‘FilterOption[]’. Type ‘FilterOption | undefined’ is not assignable to type ‘FilterOption’. Type ‘undefined’ is not assignable to type ‘FilterOption’.
100 onChange={handleChange} ~~~~
node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
21 onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
~~~~~
The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & CleanProps<"div", "value" | "invalid" | "multiple" | "disabled" | "form" | "onClose" | "defaultValue" | "onChange" | "name" | "by" | "__demoMode" | "nullable" | "immediate" | "virtual"> & OurProps<...> & { ...; } & { ...; } & { ...; }'Found 7 errors.
Hi, did you updated dependencies?
I just did it but the problem persists.
papa@salmos:/workspace/tailux/ts/demo$ ncu -u Upgrading /home/papa/workspace/tailux/ts/demo/package.json [====================] 81/81 100%
@atlaskit/pragmatic-drag-and-drop ^1.7.4 → ^1.7.7
@atlaskit/pragmatic-drag-and-drop-auto-scroll ^2.1.1 → ^2.1.2
@babel/eslint-parser ^7.28.0 → ^7.28.5
@eslint/js ^9.33.0 → ^9.39.1
@formkit/auto-animate ^0.8.2 → ^0.9.0
@headlessui/react ^2.2.7 → ^2.2.9
@hookform/resolvers ^5.2.1 → ^5.2.2
@tailwindcss/postcss ^4.1.12 → ^4.1.17
@tailwindcss/vite ^4.1.12 → ^4.1.17
@tanem/react-nprogress ^5.0.55 → ^5.0.56
@types/node ^24.2.1 → ^24.10.0
@types/react ^19.1.10 → ^19.2.2
@types/react-dom ^19.1.7 → ^19.2.2
@vitejs/plugin-react ^5.0.0 → ^5.1.0
apexcharts ^5.3.3 → ^5.3.6
axios ^1.11.0 → ^1.13.2
color ^5.0.0 → ^5.0.2
dayjs ^1.11.13 → ^1.11.19
eslint ^9.33.0 → ^9.39.1
eslint-plugin-react-hooks ^5.2.0 → ^7.0.1
eslint-plugin-react-refresh ^0.4.20 → ^0.4.24
filepond ^4.32.8 → ^4.32.10
globals ^16.3.0 → ^16.5.0
html-react-parser ^5.2.6 → ^5.2.8
i18next ^25.3.6 → ^25.6.1
lint-staged ^16.1.5 → ^16.2.6
prettier-plugin-tailwindcss ^0.6.14 → ^0.7.1
react ^19.1.1 → ^19.2.0
react-apexcharts ^1.7.0 → ^1.8.0
react-dom ^19.1.1 → ^19.2.0
react-hook-form ^7.62.0 → ^7.66.0
react-hotkeys-hook ^5.1.0 → ^5.2.1
react-i18next ^15.6.1 → ^16.2.4
react-router ^7.8.0 → ^7.9.5
react-syntax-highlighter ^15.6.1 → ^16.1.0
react-to-print ^3.1.1 → ^3.2.0
react-tooltip ^5.29.1 → ^5.30.0
swiper ^11.2.10 → ^12.0.3
tailwindcss ^4.1.12 → ^4.1.17
typescript ~5.9.2 → ~5.9.3
typescript-eslint ^8.39.1 → ^8.46.4
vite ^7.1.2 → ^7.2.2
vite-plugin-svgr ^4.3.0 → ^4.5.0
yup ^1.7.0 → ^1.7.1/*/
papa@salmos:/workspace/tailux/ts/demo$ npm run build
> react-tailux-ts-vite@1.3.2 build > tsc -b && vite build
src/app/pages/dashboards/cms-analytics/PageViews/Statistics.tsx:34:9 – error TS2322: Type ‘Dispatch<SetStateAction<Page>>’ is not assignable to type ‘(value: unknown) => void’. Types of parameters ‘value’ and ‘value’ are incompatible. Type ‘unknown’ is not assignable to type ‘SetStateAction<Page>’.
34 onChange={setSelectedPage} ~~~~
node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
21 onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
~~~~
The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & { data: DataItem[]; placeholder?: string | undefined; label?: ReactNode; displayField?: string | undefined; error?: string | ... 1 more ... | undefined; ... 11 more ...; invalid?: boolean | undefined; } & Omit<...> & RefAttributes<...>'src/app/pages/forms/KYCForm/components/DocumentType.tsx:45:9 – error TS2322: Type ‘DocumentType | null’ is not assignable to type ‘DocumentType | undefined’. Type ‘null’ is not assignable to type ‘DocumentType | undefined’.
45 value={documentTypes.find((doc) => doc.key === value) || null} ~~
node_modules/@headlessui/react/dist/components/radio-group/radio-group.d.ts:13:5
13 value?: TType;
~~~
The expected type comes from property 'value' which is declared here on type 'IntrinsicAttributes & CleanProps<"div", "value" | "disabled" | "form" | "defaultValue" | "onChange" | "name" | "by" | RadioGroupPropsWeControl> & OurProps<...> & { ...; } & { ...; } & { ...; }'src/app/pages/forms/autocomplete/Styled.tsx:32:9 – error TS2322: Type ‘Dispatch<SetStateAction<Person>>’ is not assignable to type ‘(value: unknown) => void’. Types of parameters ‘value’ and ‘value’ are incompatible. Type ‘unknown’ is not assignable to type ‘SetStateAction<Person>’.
32 onChange={setSelected} ~~~~
node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
21 onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
~~~~
The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & { data: DataItem[]; placeholder?: string | undefined; label?: ReactNode; displayField?: string | undefined; error?: string | ... 1 more ... | undefined; ... 11 more ...; invalid?: boolean | undefined; } & Omit<...> & RefAttributes<...>'src/app/pages/forms/autocomplete/StyledError.tsx:33:9 – error TS2322: Type ‘Dispatch<SetStateAction<Person[]>>’ is not assignable to type ‘(value: unknown) => void’. Types of parameters ‘value’ and ‘value’ are incompatible. Type ‘unknown’ is not assignable to type ‘SetStateAction<Person[]>’.
33 onChange={setSelected} ~~~~
node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
21 onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
~~~~
The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & { data: DataItem[]; placeholder?: string | undefined; label?: ReactNode; displayField?: string | undefined; error?: string | ... 1 more ... | undefined; ... 11 more ...; invalid?: boolean | undefined; } & Omit<...> & RefAttributes<...>'src/app/pages/forms/autocomplete/StyledHighlight.tsx:32:9 – error TS2322: Type ‘Dispatch<SetStateAction<Person[]>>’ is not assignable to type ‘(value: unknown) => void’. Types of parameters ‘value’ and ‘value’ are incompatible. Type ‘unknown’ is not assignable to type ‘SetStateAction<Person[]>’.
32 onChange={setSelected} ~~~~
node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
21 onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
~~~~
The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & { data: DataItem[]; placeholder?: string | undefined; label?: ReactNode; displayField?: string | undefined; error?: string | ... 1 more ... | undefined; ... 11 more ...; invalid?: boolean | undefined; } & Omit<...> & RefAttributes<...>'src/app/pages/forms/autocomplete/StyledMultiple.tsx:32:9 – error TS2322: Type ‘Dispatch<SetStateAction<Person[]>>’ is not assignable to type ‘(value: unknown) => void’. Types of parameters ‘value’ and ‘value’ are incompatible. Type ‘unknown’ is not assignable to type ‘SetStateAction<Person[]>’.
32 onChange={setSelected} ~~~~
node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
21 onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
~~~~
The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & { data: DataItem[]; placeholder?: string | undefined; label?: ReactNode; displayField?: string | undefined; error?: string | ... 1 more ... | undefined; ... 11 more ...; invalid?: boolean | undefined; } & Omit<...> & RefAttributes<...>'src/components/shared/table/FilterSelector.tsx:100:7 – error TS2322: Type ‘(list: FilterOption[]) => void’ is not assignable to type ‘(value: (FilterOption | undefined)[]) => void’. Types of parameters ‘list’ and ‘value’ are incompatible. Type ‘(FilterOption | undefined)[]’ is not assignable to type ‘FilterOption[]’. Type ‘FilterOption | undefined’ is not assignable to type ‘FilterOption’. Type ‘undefined’ is not assignable to type ‘FilterOption’.
100 onChange={handleChange} ~~~~
node_modules/@headlessui/react/dist/components/combobox/combobox.d.ts:21:5
21 onChange?: (value: TMultiple extends true ? EnsureArray<TValue> : TValue | null) => void;
~~~~~
The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & CleanProps<"div", "value" | "invalid" | "multiple" | "disabled" | "form" | "onClose" | "defaultValue" | "onChange" | "name" | "by" | "__demoMode" | "nullable" | "immediate" | "virtual"> & OurProps<...> & { ...; } & { ...; } & { ...; }'Found 7 errors.
So, can you send me your github username, I will add you in repo… there are latest version
Thank you so much. @alemormez
Invited
Please send invoice copy following mail ID technology@mdindia.com
Hi,
The tailux admin source files do not run the same as the demo, is there an update that is coming for me to wait and download?
Could you please confirm which folder you ran? demo or starter?
i ran demo
Just checked, everything’s working fine. Are you sure? By the way, if you share your GitHub username, I can invite you to the repo. It’s exactly the same as the demo.
the sidebar menu is not the same, its using the earlier one instead of the one used in the demo. And i prefer the new one.
here is my github @giantiss
Looks you should change your layout, there are we have 2 layout: https://tailux.piniastudio.com/docs/getting-started#layouts
Please change it and clear your ‘localstorage’.
Thanks.
I purchased the theme and installed it, but I don’t see all the menus and examples from the demo. I only see a blank layout.
How can I see the sample tables and other components?
Could you please confirm which folder you ran? demo or starter?
Hi bro, I have purchased React version. Do you have next js version..? If yes i will buy immediately
