ConfigBase
interface ConfigBase <Theme extends {} = {}> {
autocomplete?: {
templates?: Arrayable<AutoCompleteFunction | AutoCompleteTemplate>;
extractors?: Arrayable<AutoCompleteExtractor>;
};blocklist?: BlocklistRule[];
details?: boolean;
extendTheme?: Arrayable<ThemeExtender<Theme>>;
extractors?: Extractor[];
layers?: Record<string, number>;
postprocess?: Arrayable<Postprocessor>;
preflights?: Preflight<Theme>[];
preprocess?: Arrayable<Preprocessor>;
rules?: Rule<Theme>[];
safelist?: string[];
separators?: Arrayable<string>;
shortcuts?: UserShortcuts<Theme>;
sortLayers?: (layers: string[]) => string[];
theme?: Theme;
variants?: Variant<Theme>[];
}§Properties
§
autocomplete?: {
[src]templates?: Arrayable<AutoCompleteFunction | AutoCompleteTemplate>;
extractors?: Arrayable<AutoCompleteExtractor>;
}Additional options for auto complete
§
blocklist?: BlocklistRule[]
[src]Rules to exclude the selectors for your design system (to narrow down the possibilities).
Combining warnExcluded
options it can also help you identify wrong usages.
§
details?: boolean
[src]Expose internal details for debugging / inspecting
Added rules
, shortcuts
, variants
to the context and expose the context object in StringifiedUtil
You don't usually need to set this.
§
extendTheme?: Arrayable<ThemeExtender<Theme>>
[src]Custom functions to extend the theme object
§
postprocess?: Arrayable<Postprocessor>
[src]Postprocess the generate utils object
§
preprocess?: Arrayable<Preprocessor>
[src]Preprocess the incoming utilities, return falsy value to exclude
§
shortcuts?: UserShortcuts<Theme>
[src]Similar to Windi CSS's shortcuts, allows you have create new utilities by combining existing ones.
Later entries have higher priority.