Getting Started
InstallationManual InstallationChangeLogCLIDocumentationMCP Server
Foundation
Core Color SystemMapping Color SystemModsTypography
Components
Forms
FormBuilderFieldsTable Field
Buttons
ActionButtonActionsGroupButtonButtonGroupLinkButtonToggleButton
Inputs & Fields
BadgeFieldCheckboxDatePickerFieldHintFieldSectionFormStepperImageAttachmentInnerLabelFieldInputInputFieldInputOTPLabelFieldPasswordLevelRadioRadioCardSearchableSelectSearchableTreeSelectSlideDatePickerSwitchTextarea
Data Display
AvatarBadgeCalendarCardHeaderBarSectionBlockCountBadgeDividerSkeletonTableSearchableTableTextEditorTimeline
Overlays
AlertDialogContextMenuDialogDrawerDropDownMenuPopoverSpinLoadingToastTooltip
Navigation
BreadcrumbTabFormItemTabSwitchTreeDropDown
Layout
Data View
OverviewData & stateTableBoardInboxTree
Form Renderer
OverviewSectionsStepperDrawerSummaryDetail page

Manual Installation

Manual Installation

To install the TORCH Glare Components Library manually, follow these steps.

Create glare.json

Create glare.json file in the root of your project, add the following code to the file.
glare.json
1{ 2 "path": "./src" // the path where you want to install the components 3}

Configure Tailwind

Install Tailwind css, configure your tailwindcss and try it functionality first then run this commands to install the required dependencies for tailwind css

For Tailwind CSS version 4

If you are using Tailwind CSS version 4, you need to add the following dependencies to your project.
npm install glare-typography@latest mapping-color-system-v4@latest glare-torch-mode@latest
Optional plugins but recommended
npm install tailwindcss-animate tailwind-scrollbar-hide
Then add the following code to your global.css file. Every @import must come BEFORE the @plugin rules — CSS requires imports to precede other at-rules, so a bundler silently drops any that come later, which would remove the colour variables and the radius / container / breakpoint scales.
global.css
1@import "tailwindcss"; 2@import "mapping-color-system-v4/tailwindVars.css"; 3@import "glare-torch-mode/theme.css"; 4@plugin "glare-torch-mode"; 5@plugin "tailwind-scrollbar-hide"; 6@plugin "tailwindcss-animate"; 7@plugin "glare-typography"; 8@plugin "mapping-color-system-v4";
The theme.css import is required, and needs glare-torch-mode 1.4.0 or newer. The plugin itself only registers the colour variables; the corner-radius scale, the container sizes and the custom breakpoints reach Tailwind through theme.extend in a JavaScript config, which version 4 does not have. Without this import the rounded-radius classes used by Button, Badge, Input, ActionButton, Select and TextArea are never generated, so those components render with square corners, and the sm and @md variants silently fall back to Tailwind's own values.
Two things to be aware of in version 4. Tailwind shares the container scale with the max-w utilities, so setting the md container to 650px also makes max-w-md 650px. And the plugin sets its radius variables on the root element, which is Tailwind 4's own border-radius namespace — the values match its defaults (2, 4, 6, 8, 12, 16, 24 and 32px), but they are declared in pixels where Tailwind uses rem, so they stop matching if you change the root font size.
If you are pinned to an older glare-torch-mode, paste this into your global.css instead of the theme.css import above — it is exactly what the file contains.
global.css
1@theme { 2 /* Corner radius — yields rounded-radius-* */ 3 --radius-radius-none: 0px; 4 --radius-radius-xs: 2px; 5 --radius-radius-sm: 4px; 6 --radius-radius-md: 6px; 7 --radius-radius-lg: 8px; 8 --radius-radius-xl: 12px; 9 --radius-radius-2xl: 16px; 10 --radius-radius-3xl: 24px; 11 --radius-radius-4xl: 32px; 12 --radius-radius-5xl: 40px; 13 --radius-radius-6xl: 48px; 14 --radius-radius-round: 9999px; 15 16 /* Container-query sizes for the @md: variants used by FieldSection / FormRenderer */ 17 --container-xs: 320px; 18 --container-sm: 600px; 19 --container-md: 650px; 20 --container-lg: 1024px; 21 --container-xl: 1280px; 22 --container-2xl: 1536px; 23 24 /* Viewport breakpoints — sm is 600px rather than Tailwind's 640 */ 25 --breakpoint-sm: 600px; 26 --breakpoint-md: 768px; 27 --breakpoint-lg: 1024px; 28 --breakpoint-xl: 1280px; 29 --breakpoint-2xl: 1536px; 30}

For Tailwind CSS version 3

Version 3 uses mapping-color-system (not the -v4 package), and needs the container-queries plugin. Install these instead of the version 4 dependencies above — glare-typography, tailwindcss-animate and tailwind-scrollbar-hide are shared by both.
npm install mapping-color-system@latest glare-torch-mode@latest @tailwindcss/container-queries
tailwind.config.js
1const { plugin, mappingVars } = require('mapping-color-system') 2// Design tokens plus the shared radius / container / screen scales. 3const torchMode = require('glare-torch-mode') 4 5module.exports = { 6 content: [ 7 ... 8 // put your path that your use in glare.json file. for example: 9 "./src/**/*.{js,ts,jsx,tsx,mdx}", 10 ], 11 theme: { 12 extend: { 13 colors: mappingVars, 14 borderRadius: torchMode.borderRadius, 15 containers: torchMode.containers, 16 }, 17 }, 18 // Top level, not inside extend — this replaces Tailwind's breakpoints. 19 screens: torchMode.screens, 20 plugins: [ 21 plugin, 22 require('@tailwindcss/container-queries'), 23 require('tailwindcss-animate'), 24 require('tailwind-scrollbar-hide'), 25 require('glare-typography'), 26 torchMode, 27 function ({ addVariant }) { 28 addVariant("rtl", ['&[dir="rtl"]', '[dir="rtl"] &']); 29 addVariant("ltr", ['&[dir="ltr"]', '[dir="ltr"] &']); 30 }, 31 ], 32};
Make sure to add the following code to your tailwind.config.ts file.
  • specify the path of the components in tailwind config file.
  • add the plugins to the plugins array.
  • add the mappingVars to the extend components colors object.
  • add borderRadius and containers from glare-torch-mode. borderRadius is what produces the rounded-radius classes the components are built on — without it they render with square corners.
  • set screens at the top level rather than inside extend, so Glare's breakpoints replace Tailwind's rather than being added alongside them.
  • include the container-queries plugin. FormBuilder and FormRenderer mark their root as a container and lay fields out with @md variants; without the plugin those compile to nothing.
  • register the rtl and ltr variants with both selectors. The self-only form matches an element carrying the dir attribute itself, so an rtl class on a component nested inside an RTL wrapper would never apply.

Include Remix Icons & SF Pro Font

Add Remix Icons CDN and SF Pro Font to your html head section for icons support and font standardization.
index.html
1<head> 2 <link 3 href="https://cdn.jsdelivr.net/npm/[email protected]/fonts/remixicon.css" 4 rel="stylesheet" 5 /> 6 <link 7 rel="stylesheet" 8 href="https://cdn.statically.io/gh/TORCH-Corp/SF-PRO-FONT/main/font/fonts.css" 9 /> 10 <link 11 rel="preload" 12 href="https://cdn.statically.io/gh/TORCH-Corp/SF-PRO-FONT/main/font/SF-Pro.woff2" 13 as="font" 14 type="font/woff2" 15 /> 16</head>

Adding Components

Now, you can start adding components to your project, run the following command to install the TORCH Glare Components.
Note: This command will make dropdown list of available components.
npx torch-glare@latest add
or specify the components you want to install.
npx torch-glare@latest add Button

Usage

App.tsx
1import { Button } from "./Button"; 2function App() { 3 return ( 4 <Button variant="PrimeStyle" size="M"> 5 Click Me 6 </Button> 7 ); 8}

Common Problems

Components Without Style

If you install the components and get a styleless component, then the issue is definitely with Tailwind CSS. Double-check your Tailwind version and configuration, re-read the Tailwind CSS installation guide.
Tailwind Configurations

Components Without Icons

If you get a component without icons, then the issue is definitely with Remix Icons. Double-check your Remix Icons installation and re-read the Remix Icons installation guide above.
Icons installation

CLI Errors

You may face some issues with the CLI if you're using a different package manager instead of npm. Try removing the `node_modules` and lock files, then reinstall the dependencies using only your preferred package manager. We recommend using pnpm or Yarn for a smoother installation experience.
Try to run this command to remove node_modules and package-lock.json and then use your favorite package manager.
rm -rf node_modules package-lock.json