origam 2.18.0 → 2.18.2

package/dist/src/utils/Commons/color.util.d.ts

@@ -492,26 +492,3 @@ export declare function warnDeprecatedProp(component: string, oldProp: string, n
  * bullishColor/bearishColor").
  ********************************************************/
 export declare function warnUnsupportedProp(component: string, prop: string, reason: string): void;
-/*********************************************************
- * warnDeprecatedEmit
- *
- * @description
- * Warn (once per component / emit, dev builds only) that the consumer
- * attached a listener to an emit scheduled for removal. The emit KEEPS
- * FIRING until the removal version — this announces the break instead of
- * shipping it. `replacement` should name what to do instead, not merely
- * say the emit is going away. Same once-per-key cache as the three
- * warnings above, but for a public EMIT rather than a prop.
- *
- * @description
- * First use case: `click:prepend` / `click:append` on `<OrigamBtn>` (#443).
- * Those two were reachable by MOUSE ONLY — the emit is bound to a
- * descendant span, while keyboard activation synthesises its click on the
- * button root. The `role="button"` + tab-stop remedy `useAdjacent` applies
- * on the other ten consumers is ILLEGAL here: Btn's root is a
- * `<button>`/`<a>`, whose content model forbids both an interactive
- * descendant and any descendant carrying `tabindex`. A control that already
- * owns one action cannot host a second — two actions are two buttons
- * (`origam-btn-group`).
- ********************************************************/
-export declare function warnDeprecatedEmit(component: string, emit: string, replacement: string, removalVersion?: string): void;

package/dist/src/utils/Commons/color.util.js

@@ -343,14 +343,3 @@ export function warnUnsupportedProp(component, prop, reason) {
     `[origam] <${component}> prop "${prop}" has no effect on this component: ${reason}`
   );
 }
-const _warnedDeprecatedEmitKeys = /* @__PURE__ */ new Set();
-export function warnDeprecatedEmit(component, emit, replacement, removalVersion = "v3.0.0") {
-  if (typeof console === "undefined") return;
-  if (!import.meta.env?.DEV) return;
-  const key = `${component}::${emit}`;
-  if (_warnedDeprecatedEmitKeys.has(key)) return;
-  _warnedDeprecatedEmitKeys.add(key);
-  console.warn(
-    `[origam] <${component}> emit "${emit}" is deprecated and will be removed in ${removalVersion}. ${replacement}`
-  );
-}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "origam",
-  "version": "2.18.0",
+  "version": "2.18.2",
   "type": "module",
   "description": "origam — a Vue 3 design system with multi-theme design tokens, CSS-first components and TypeScript types.",
   "keywords": [

package/dist/src/consts/Btn/btn.const.cjs

@@ -1,7 +0,0 @@
-"use strict";
-
-Object.defineProperty(exports, "__esModule", {
-  value: true
-});
-exports.ADJACENT_EMIT_REPLACEMENT = void 0;
-const ADJACENT_EMIT_REPLACEMENT = exports.ADJACENT_EMIT_REPLACEMENT = "It was never reachable by keyboard (the emit fires from a descendant span, and keyboard activation targets the button root), and Btn cannot be given a focusable sub-control because <button>/<a> forbid interactive descendants. Use two buttons in an <origam-btn-group> instead. The prepend/append slots themselves are unaffected.";

package/dist/src/consts/Btn/btn.const.d.ts

@@ -1,32 +0,0 @@
-/*********************************************************
- * ADJACENT_EMIT_REPLACEMENT
- *
- * @description
- * Guidance shown when a consumer attaches `click:prepend` / `click:append`
- * to `<OrigamBtn>` — both deprecated (#443), removed in v3.0.0.
- *
- * @description
- * They were a documented, story-demonstrated API that NO keyboard user
- * could ever reach. The emits fire from a `@click` bound to the
- * `origam-btn__prepend` / `origam-btn__append` `<span>`; a keyboard
- * activation synthesises its click on the component ROOT, so the event
- * never reaches a listener bound to a descendant.
- *
- * @description
- * ⛔ The remedy `useAdjacent` applies on the other ten consumers — turn the
- * zone into a real `role="button"` tab stop when a listener is attached —
- * is ILLEGAL here, and that is why Btn is the one component that has to
- * drop the emit instead of fixing it. Btn's root renders as `<button>` or
- * `<a>`, and the HTML content model for both forbids any interactive
- * content descendant AND any descendant carrying a `tabindex` attribute.
- * A nested `<button type="button">` is invalid at that position for the
- * same reason.
- *
- * @description
- * The shape was wrong, not merely the markup: a control that already owns
- * one action cannot host a second. Two actions are two buttons — compose
- * them with `<origam-btn-group>`. The `prepend` / `append` SLOTS are
- * untouched and stay entirely legitimate for decorative or informational
- * content.
- ********************************************************/
-export declare const ADJACENT_EMIT_REPLACEMENT = "It was never reachable by keyboard (the emit fires from a descendant span, and keyboard activation targets the button root), and Btn cannot be given a focusable sub-control because <button>/<a> forbid interactive descendants. Use two buttons in an <origam-btn-group> instead. The prepend/append slots themselves are unaffected.";

package/dist/src/consts/Btn/btn.const.js

@@ -1 +0,0 @@
-export const ADJACENT_EMIT_REPLACEMENT = "It was never reachable by keyboard (the emit fires from a descendant span, and keyboard activation targets the button root), and Btn cannot be given a focusable sub-control because <button>/<a> forbid interactive descendants. Use two buttons in an <origam-btn-group> instead. The prepend/append slots themselves are unaffected.";