@poly-x/react 0.1.0-alpha.12 → 0.1.0-alpha.14

package/dist/index.cjs

@@ -1024,7 +1024,7 @@ const DEFAULT_LABELS$2 = {
 	submit: "Send reset link",
 	submitting: "Sending…",
 	sentHeading: "Check your email",
-	sentSubheading: "If an account exists for {email}, a password reset link is on its way. It expires in 30 minutes.",
+	sentSubheading: "If an account exists for {email}, a password reset link is on its way — it expires in 30 minutes. If it doesn't arrive within a few minutes, check your spam folder, then contact your workspace administrator.",
 	differentEmail: "Use a different email",
 	backToSignIn: "Back to sign in",
 	securedBy: "Secured by PolyX",

package/dist/index.d.cts

@@ -292,7 +292,13 @@ interface ForgotPasswordLabels {
   submitting: string;
   /** Shown after submit — always, regardless of whether the account exists. */
   sentHeading: string;
-  /** Confirmation body. `{email}` is replaced with the entered address, emphasized. */
+  /**
+   * Confirmation body. `{email}` is replaced with the entered address, emphasized.
+   * Kept deliberately uniform (no account-existence / mail-config signal, per the
+   * anti-enumeration reset design) and points the user at their administrator for
+   * the cases where no mail can arrive (org has reset email disabled, no provider
+   * configured, or a send failure) — none of which the response is allowed to reveal.
+   */
   sentSubheading: string;
   differentEmail: string;
   backToSignIn: string;

package/dist/index.d.mts

@@ -292,7 +292,13 @@ interface ForgotPasswordLabels {
   submitting: string;
   /** Shown after submit — always, regardless of whether the account exists. */
   sentHeading: string;
-  /** Confirmation body. `{email}` is replaced with the entered address, emphasized. */
+  /**
+   * Confirmation body. `{email}` is replaced with the entered address, emphasized.
+   * Kept deliberately uniform (no account-existence / mail-config signal, per the
+   * anti-enumeration reset design) and points the user at their administrator for
+   * the cases where no mail can arrive (org has reset email disabled, no provider
+   * configured, or a send failure) — none of which the response is allowed to reveal.
+   */
   sentSubheading: string;
   differentEmail: string;
   backToSignIn: string;

package/dist/index.mjs

@@ -1023,7 +1023,7 @@ const DEFAULT_LABELS$2 = {
 	submit: "Send reset link",
 	submitting: "Sending…",
 	sentHeading: "Check your email",
-	sentSubheading: "If an account exists for {email}, a password reset link is on its way. It expires in 30 minutes.",
+	sentSubheading: "If an account exists for {email}, a password reset link is on its way — it expires in 30 minutes. If it doesn't arrive within a few minutes, check your spam folder, then contact your workspace administrator.",
 	differentEmail: "Use a different email",
 	backToSignIn: "Back to sign in",
 	securedBy: "Secured by PolyX",

package/dist/styles.css

@@ -10,8 +10,33 @@
  * (`:root`, a wrapper div, …) — that is the supported theming surface. Dark mode
  * follows the OS by default and defers to an explicit `.dark` / `[data-theme]`
  * on a host ancestor when one is present.
+ *
+ * ---------------------------------------------------------------------------
+ * Cascade: everything here lives in the `polyx` layer, and that is load-bearing.
+ *
+ * Unlayered CSS beats layered CSS outright — not by specificity, but by rank; no
+ * import order or selector weight changes it. Shipping these rules unlayered
+ * therefore beat every Tailwind utility a host wrote (Tailwind emits utilities
+ * into `@layer utilities`), so `className`/`triggerClassName` silently did
+ * nothing and hosts were pushed toward `!important`. Layering hands that control
+ * back: a host's utilities and unlayered CSS both outrank us now.
+ *
+ * The statement below fixes where `polyx` sits. It must land AFTER `base` —
+ * Tailwind's preflight puts `*, ::before, ::after { border: 0 solid }` there, and
+ * that would erase our own borders if we ranked lower — and BEFORE `utilities`,
+ * so host utilities still win. Naming Tailwind's layers costs nothing when the
+ * host doesn't use Tailwind: the names simply resolve to empty layers.
+ *
+ * Layer order is set by first declaration, so this only holds if our stylesheet
+ * is imported BEFORE the host's Tailwind entry. Import it later and `polyx` is
+ * appended last, which puts us back to outranking utilities — no worse than the
+ * unlayered behaviour, but not the fix either. Import us first.
  */
 
+@layer theme, base, polyx, components, utilities;
+
+@layer polyx {
+
 .polyx-signin {
 	/* Colors */
 	--polyx-brand: #4f46e5;
@@ -683,3 +708,8 @@
 	height: 1rem;
 	color: var(--polyx-muted-fg);
 }
+
+/* Closes `@layer polyx` — opened at the top of the file. The rules above are left
+   unindented deliberately: wrapping the sheet in a layer is a cascade change, not a
+   reformat, and re-indenting 600 lines would bury it in the diff. */
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@poly-x/react",
-  "version": "0.1.0-alpha.12",
+  "version": "0.1.0-alpha.14",
   "description": "PolyX SDK for React SPAs - provider, hooks, drop-in auth UI",
   "license": "MIT",
   "type": "module",
@@ -27,7 +27,7 @@
   "module": "./dist/index.mjs",
   "types": "./dist/index.d.cts",
   "dependencies": {
-    "@poly-x/core": "0.1.0-alpha.12"
+    "@poly-x/core": "0.1.0-alpha.14"
   },
   "peerDependencies": {
     "react": ">=18",