@astryxdesign/core 0.1.0 → 0.1.1-canary.129bf0e

package/src/theme/tokens.ts

@@ -16,7 +16,7 @@
  */
 
 import {
-  xdsTokenDefaults,
+  tokenDefaults,
   type DefinedTheme,
   type TokenName,
   type TokenValue,
@@ -60,7 +60,7 @@ export function tokenVar(name: TokenName | (string & {})): string {
 
 /** Flat map of every known Astryx token name to its `var(--token-name)` reference. */
 export const tokenVars: Record<TokenName, string> = Object.fromEntries(
-  Object.keys(xdsTokenDefaults).map(name => [name, tokenVar(name)]),
+  Object.keys(tokenDefaults).map(name => [name, tokenVar(name)]),
 ) as Record<TokenName, string>;
 
 /**
@@ -147,7 +147,7 @@ function resolveXDSTokenValue(
 /**
  * Resolve all Astryx token values for a theme and effective color mode.
  *
- * The result starts with `xdsTokenDefaults`, applies `theme.tokens`, then
+ * The result starts with `tokenDefaults`, applies `theme.tokens`, then
  * reapplies `theme.__inputTokens` when available so explicit tuple overrides
  * retain their original light/dark sides instead of relying on CSS parsing.
  * This mirrors the token resolution used by `useTheme()` but does not need
@@ -162,7 +162,7 @@ export function resolveThemeTokens(
   const {mode} = options;
   const resolved: Record<string, string> = {};
 
-  for (const [key, value] of Object.entries(xdsTokenDefaults)) {
+  for (const [key, value] of Object.entries(tokenDefaults)) {
     resolved[key] = resolveXDSTokenValue(value, mode);
   }
 

package/src/theme/useTheme.ts

@@ -63,7 +63,7 @@ export interface UseThemeReturn {
    * For tokens with [light, dark] tuples, returns the value matching
    * the current mode. For single-value tokens, returns the value as-is.
    *
-   * Falls back to xdsTokenDefaults if the token isn't overridden by the theme.
+   * Falls back to tokenDefaults if the token isn't overridden by the theme.
    *
    * @example
    * ```
@@ -75,7 +75,7 @@ export interface UseThemeReturn {
   /**
    * All tokens resolved for the current color mode.
    *
-   * Merges xdsTokenDefaults with the theme's overrides, resolving
+   * Merges tokenDefaults with the theme's overrides, resolving
    * light-dark() values based on the effective color mode.
    *
    * Memoized — stable reference unless theme or mode changes.

package/src/utils/dateParser.test.ts

@@ -320,5 +320,31 @@ describe('parseDateInput', () => {
     it('rejects mixed separators', () => {
       expect(parseDateInput('1/25.2026')).toBeNull();
     });
+
+    it('treats a single typed digit as incomplete, not a date', () => {
+      // A user starting to type a month (e.g. "0" or "1" for January) should
+      // not produce a date. Native Date parsing would otherwise coerce these
+      // into arbitrary dates (and a year of 0 in some engines).
+      expect(parseDateInput('0')).toBeNull();
+      expect(parseDateInput('1')).toBeNull();
+    });
+
+    it('treats bare numeric input as incomplete, not a date', () => {
+      expect(parseDateInput('00')).toBeNull();
+      expect(parseDateInput('01')).toBeNull();
+      expect(parseDateInput('12')).toBeNull();
+      expect(parseDateInput('2026')).toBeNull();
+    });
+
+    it('never returns an out-of-range date for partial input', () => {
+      // Regression: partial input must never yield a date with year < 1,
+      // which would throw when later re-parsed and crash the page.
+      for (const input of ['0', '1', '01', '00', '9', '99']) {
+        const result = parseDateInput(input);
+        if (result !== null) {
+          expect(result.year).toBeGreaterThanOrEqual(1);
+        }
+      }
+    });
   });
 });

package/src/utils/dateParser.ts

@@ -124,10 +124,24 @@ export function parseDateInput(input: string): PlainDate | null {
     return parseNumericDate(+first, +second, currentYear);
   }
 
-  // 6. Fall back to native Date parsing for other formats
+  // 6. Fall back to native Date parsing for other formats.
+  //
+  // Skip bare numeric input (e.g. "0", "1", "01", "2026"). These are
+  // in-progress values a user is still typing, not complete dates. Native
+  // `Date` parsing coerces them into arbitrary dates ("0" -> year 2000 in V8,
+  // year 0 in some engines), which is both surprising and — when the year
+  // resolves to 0 — produces an out-of-range date that throws downstream.
+  // Treat them as not-yet-a-valid-date instead.
+  if (/^\d+$/.test(trimmed)) {
+    return null;
+  }
+
   const parsed = new Date(trimmed);
   if (!isNaN(parsed.getTime())) {
-    return plainDateFromDate(parsed);
+    const fromDate = plainDateFromDate(parsed);
+    // Validate the result so we never return an out-of-range date (e.g. a
+    // year of 0), which would throw when later re-parsed.
+    return tryCreatePlainDate(fromDate.year, fromDate.month, fromDate.day);
   }
 
   return null;

package/dist/DropdownMenu/renderXDSDropdownItems.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"renderXDSDropdownItems.d.ts","sourceRoot":"","sources":["../../src/DropdownMenu/renderXDSDropdownItems.tsx"],"names":[],"mappings":"AAEA;;;;GAIG;AAEH,OAAO,KAAK,EAAC,SAAS,EAAC,MAAM,OAAO,CAAC;AAUrC,OAAO,KAAK,EAEV,kBAAkB,EAEnB,MAAM,gBAAgB,CAAC;AAyBxB;;;GAGG;AACH,wBAAgB,sBAAsB,CACpC,KAAK,EAAE,kBAAkB,EAAE,GAC1B,SAAS,CA8CX"}