Nebular is a customizable, MIT-licensed Angular UI library built on the Eva Design System, aimed at Angular teams that need a ready-made component kit with multiple visual themes and dark mode support they can adapt to their own brand.

What it is

Nebular is an open-source UI library for Angular, distributed as the @nebular/theme npm package and written in TypeScript. It is based on the Eva Design System specifications and ships with four visual themes, including a dark theme, along with a theming engine that supports runtime theme switching and a custom CSS properties mode. Its component set covers more than thirty-five Angular UI components, each configurable by colors, sizes, appearances, and shapes, and it includes an authentication and security layer with three configurable auth strategies. The project lives in the Angular ecosystem and is developed by Akveo, the same organisation behind Eva Icons and the ngx-admin starter.

The concrete problem it solves is the assembly work that otherwise sits in front of every Angular application: a team that needs an admin interface, a login flow, and a coherent visual identity normally has to build or stitch together components, theme handling, and an auth layer before writing any product code. Nebular replaces that accumulation of ad-hoc pieces with one library that supplies components, theming, icons, and authentication together, so the look and feel can be changed through configuration rather than through rewriting stylesheet by stylesheet. It also fills the gap left when a design system exists only as specification: Nebular implements Eva Design System rules as usable Angular components.

Key capabilities

• Four visual themes, including a dark theme, that can be customized to a brand rather than used as fixed presets.
• A theming engine with runtime theme switching and a custom CSS properties mode.
• More than thirty-five Angular UI components with configurable colors, sizes, appearances, and shapes.
• Three authentication strategies and a security layer that can be configured for an existing API.
• SVG Eva Icons support with over 480 general-purpose icons.
• Installation through Angular CLI with ng add @nebular/theme, which configures the project automatically.
• Companion starter applications, ngx-admin and ngx-admin-starter, built on Nebular modules.

Who uses it and how

• Angular teams building administrative dashboards and internal tools that need a component kit, authentication screens, and theming without assembling them from separate sources.
• Product teams that need to white-label an interface: the theming engine and custom CSS properties mode allow brand colors and appearances to change without editing the component implementations.
• Applications requiring more than one visual mode, using runtime theme switching to move between light and dark presentations.
• Projects that need identity and access handled early: the three auth strategies and security layer can be wired to an existing API instead of being written from scratch.
• Teams starting from a template, using ngx-admin (described in the README as a 20k+ star application with e-commerce and IoT components) or the lighter ngx-admin-starter, or evaluating the library in a Stackblitz template.

Getting started

The documented quick start is ng add @nebular/theme through the Angular CLI, which performs the configuration automatically, with a manual setup guide available for teams that want more control over the process.

How it compares

This registry's facts name no direct equivalent to Nebular, so it stands alone here rather than sitting in a field of comparable Angular UI libraries. The closest named projects are not alternatives but dependants: ngx-admin and ngx-admin-starter are applications built on Nebular modules, and Eva Icons is a sibling icon set from the same organisation rather than a competing component library.

When to use it — and when not to

Nebular is a reasonable choice for an Angular project that wants components, theming, and an auth layer from a single MIT-licensed dependency and does not need upstream responsiveness. It is a poor fit for anyone who needs active maintenance or timely issue resolution: the README states the repository is in a state of minimal maintenance, with effort focused solely on keeping the Angular version current, no active review or merging of pull requests, and no responses to issues, while 932 open issues remain. Teams that depend on prompt fixes, new features, or a roadmap should look elsewhere, and anyone needing support for frameworks other than Angular should not consider it at all.

ng add @nebular/theme