Changelog

Have something to say?

Tell NextUI Pro how they could make the product more useful to you.

Hero UI Pro -> only version 2?

Hi HeroUI team, I purchased HeroUI Pro for $399 and noticed a contradiction in the documentation: HeroUI Pro requires HeroUI v2 or higher At the same time, v2 is marked as deprecated and v3 is recommended for new projects HeroUI Pro is currently not available for v3? Tables etc … This leaves Pro customers without a clear recommendation on which version to use. Is there a roadmap for HeroUI Pro supporting v3, or a recommended transition path?

RAS Technologies GmbH About 2 months ago

4

πŸ“₯ Feedback

Kanban Board

Can you add a DND kanban board component? It would be made of the following. This is an example structure of what it could looklike // this some really basic divs but in theory you could style the item in any way // you want Client Name: James Holt Conversion Amount: $4000 Contract Number: 1231 Some other entry Client Name: Hellen Turd Conversion Amount: $0 Contract Number: 1244 Some other entry

Alex Klusa 4 months ago

πŸ’‘ Feature Request

Remove `useCallback` usage from the HeroProUI components

useCallback is very dangerous to use, you just need to miss adding a dependency in the array and you broke your app, debugging is a nightmare. useCallback is not needed if you never put a function inside a dependency of useEffect, useCallback, useMemo. React compiler is coming soon and will remove the need for it anyway.

Morse 9 months ago

πŸ“₯ Feedback

Heroui Monorepo Boilerplate

This monorepo template for the Heroui project is designed for modular feature development, streamlined testing, and scalability. It includes pre-configured Git hooks (using Husky), workspaces, and a well-organized project structure that separates component overrides, global utilities, and hooks at the root level. Note: This is a general example. You may choose to implement more optimal or customized solutions depending on your project's needs. Recommended Tools and Workspaces Workspaces: Use Yarn Workspaces (or npm Workspaces) to manage dependencies efficiently across packages. Lerna: Integrate Lerna to orchestrate versioning and execute scripts (like build and test) across all subprojects. Project Structure php heroui-monorepo/ β”œβ”€β”€ library/ # Overrides for components when needed β”œβ”€β”€ utils/ # Global utilities shared across packages β”œβ”€β”€ hooks/ # Global programmatic hooks (e.g., custom React hooks or automation scripts) β”œβ”€β”€ packages/ # Project-specific packages β”‚ β”œβ”€β”€ heroui-core/ # Core functionality of Heroui β”‚ └── heroui-feature-new/ # Example of a new feature package β”œβ”€β”€ .husky/ # Pre-configured Git hooks (e.g., pre-commit) β”œβ”€β”€ package.json # Root package configuration (workspaces, scripts, dependencies) └── README.md # Project title and detailed description Detailed Component Description library/: Contains overrides for components. This centralized folder allows you to modify or enhance standard Heroui components across multiple packages. utils/: Stores global utilities and helper functions (like logging, data formatting, and common computations) that can be reused in any package within the monorepo. hooks/: Houses custom hooks and automation scripts that are used throughout the project. This folder can include both React hooks and other specialized scripts. (Note: Git hooks remain configured in the.husky/ folder.) packages/: Contains individual modules or features of the project. Each package, such as heroui-core (the core functionality) and heroui-feature-new (an example feature), has its own package.json for managing package-specific dependencies and scripts. .husky/: Pre-configured with Git hooks to enforce code quality through tasks such as linting, testing, and formatting checks before commits. Root package.json: Defines the workspace settings, global scripts (like build, test, and prepare for Husky), and dependencies (such as Lerna and Husky), ensuring that the entire project benefits from a unified configuration. README.md: Provides the project title and a detailed description, outlining the purpose, structure, and key features of the monorepo. Benefits and Considerations Modularity and Overrides: The library/ folder allows centralized management and overrides of components, ensuring consistency across various modules. Code Reusability: The utils/ folder promotes reuse of common logic and utilities, reducing duplication and maintaining consistency. Custom Automation: The hooks/ folder enables the implementation of custom automation and programmatic hooks, complementing the Git hooks set up in.husky/. Scalability: The monorepo structure supports seamless addition of new features or packages, keeping the project organized as it grows. Automated Quality Assurance: Pre-configured Git hooks and Lerna integration help automate testing and linting, ensuring high code quality and reducing the likelihood of production issues.

Максим Π“ΡƒΠΌΠ΅Π½ΡŽΠΊ 10 months ago

1

πŸ’‘ Feature Request

Expand Data Visualization Components

I’d love to see more variety in the data chart components. My customers care a lot about data visuals, and while Hero UI looks great, it’s too limited for presentations at its current state regarding data charts. Something more like shadcn’s wide range of charts would be super helpfulβ€”makes it easier to sell and keeps things looking modern without needing extra libraries. reference link: shadecn

Kazi 11 months ago

πŸ“ Components Request