@kbach/react-native 1.0.0-beta.5 → 1.0.0-beta.51

package/dist/index.web.d.ts

@@ -1,7 +1,104 @@
-import { StyleObject } from './index.js';
-export { ThemeConfig, ThemeContextValue, ThemeMode, ThemeProvider, ThemeProviderProps, defaultTheme, getGlobalDarkMode, getGlobalThemeMode, getTheme, setGlobalThemeMode, setTheme, subscribeGlobalDarkMode, toggleGlobalDarkMode, useGlobalDarkMode, useTheme } from './index.js';
+export { ColorEntry, ContainerConfig, ThemeConfig, defaultTheme, getTheme, setTheme } from './theme';
+export { C as ClassArray, a as ClassDictionary, b as ClassValue, c as ColorScale, d as ColorsAPI, K as KbachConfig, T as ThemeProvider, e as ThemeProviderProps, f as ThemeState, h as applyKbachConfig, i as clsx, r as resolveKbachConfig, u as useColors, j as useDynamicToken, k as useTheme } from './clsx-BLLSnqAa.js';
+export { ThemeMode, getGlobalDarkMode, getGlobalThemeMode, setGlobalThemeMode, subscribeGlobalDarkMode, toggleGlobalDarkMode } from './darkModeStore';
+export { deleteDynamicToken, getDynamicToken, setDynamicToken, subscribeDynamicTokens } from './dynamicTokens';
 import 'react';
 
-declare function resolveStyle(classString: string, pressed?: boolean): StyleObject;
+/**
+ * Resolves `classString` to CSS via the WASM engine, injects every returned
+ * rule into a shared `<style data-kbach-rn>` tag (cascade-order-safe — see
+ * cssInjector.web.ts), and returns the class string to use as
+ * `dataSet={{ kb: <returned value> }}`. MUST use the returned value, not the
+ * original input — mode-aware color names (e.g. `bg-surface`) expand into a
+ * literal light/dark pair, and the generated rules target that expanded
+ * text, not the original.
+ */
+declare function resolveClassName(classString: string): string;
 
-export { StyleObject, resolveStyle };
+export { resolveClassName };
+
+/**
+ * Ambient module augmentation adding `className?: string` to React
+ * Native's own component prop types — without this, `<View
+ * className="...">` type-checks fine at RUNTIME (the babel plugin/
+ * jsx-runtime accept `className` on ANY host element regardless of its
+ * declared prop type — see jsxRuntimeCore.ts's own `processElement` doc
+ * comment) but fails `tsc`/editor type-checking, since `ViewProps`/
+ * `TextProps`/etc. (react-native's own types) have no `className` field at
+ * all. Confirmed as a real, reported gap: nothing in this package shipped
+ * this augmentation before, so a React Native CLI project running `tsc`
+ * (or just seeing red squiggles in-editor) hit "Property 'className' does
+ * not exist on type ... ViewProps ..." on every styled element.
+ *
+ * A plain `.d.ts` file has no effect on its own unless something actually
+ * pulls it into a consumer's type-checking. A side-effect `import
+ * './rnClassNameTypes'` from index.ts was the first thing tried here, but
+ * tsup's dts rollup (rollup-plugin-dts) tree-shakes a side-effect-only
+ * import with nothing it can trace a type reference through — confirmed by
+ * hand that this wasn't even consistent (survived one build, silently
+ * vanished from an immediately-following clean rebuild of the identical
+ * source). `scripts/append-classname-types.mjs` appends this file's own
+ * text onto the end of the built `dist/index.d.ts`/`dist/index.web.d.ts`
+ * directly as a deterministic post-build step instead — see that script's
+ * own doc comment. Anyone who imports ANYTHING from '@kbach/react-native'
+ * gets it with no extra tsconfig step needed either way. Same underlying
+ * problem (and the interface-merge half of this fix) nativewind — a React
+ * Native styling library solving this identical className-typing problem —
+ * also has to solve.
+ *
+ * Every interface below is `export interface XProps extends Readonly<...>
+ * {}` in react-native's own generated types (RN >= ~0.81's Flow-to-TS
+ * generation, `types_generated/`) — an otherwise-empty body, so merging a
+ * member in is exactly as safe as against a hand-written interface.
+ * Deliberately NOT listed here: `ImageProps`, `TouchableOpacityProps`,
+ * `ModalProps` — these are `export type X = Readonly<...>` TYPE ALIASES in
+ * the same generated types, which TypeScript cannot declaration-merge into
+ * at all (confirmed by hand: attempting it is a flat "Duplicate identifier"
+ * compile error, not a silent no-op). They don't need an entry anyway —
+ * confirmed against a real `tsc` run (RN 0.87) that `className` on
+ * `Image`/`TouchableOpacity`/`TouchableHighlight`/`Modal`/`SafeAreaView`
+ * ALL already type-check cleanly once `ViewProps` and
+ * `TouchableWithoutFeedbackProps` below are augmented — each of those
+ * components' real prop type composes one or the other somewhere in its
+ * own `Omit<...> & ...` chain (`SafeAreaView` in particular turned out to
+ * reuse `ViewProps` directly, with no separate props type of its own at
+ * all), so the merged `className` field flows through without needing its
+ * own dedicated entry.
+ */
+export {};
+
+declare module 'react-native' {
+  interface ViewProps {
+    className?: string;
+  }
+  interface TextProps {
+    className?: string;
+  }
+  interface ScrollViewProps {
+    className?: string;
+  }
+  interface PressableProps {
+    className?: string;
+  }
+  interface TextInputProps {
+    className?: string;
+  }
+  interface TouchableHighlightProps {
+    className?: string;
+  }
+  interface TouchableWithoutFeedbackProps {
+    className?: string;
+  }
+  interface SwitchProps {
+    className?: string;
+  }
+  interface KeyboardAvoidingViewProps {
+    className?: string;
+  }
+  interface FlatListProps<ItemT> {
+    className?: string;
+  }
+  interface SectionListProps<ItemT, SectionT> {
+    className?: string;
+  }
+}