@swisspost/design-system-components 10.0.0-next.54 → 10.0.0-next.56

package/dist/types/home/runner/work/design-system/design-system/packages/components/.stencil/prebuild.d.ts

@@ -0,0 +1,9 @@
+interface ComponentNameOutputOptions {
+    type: 'json' | 'scss';
+    template: string;
+    lineSeparator: string;
+    formatParser: 'json' | 'scss' | null;
+}
+export declare const componentNameOutputOptions: Partial<ComponentNameOutputOptions>[];
+export declare function createComponentNameOutput(outputOptionsArray: Partial<ComponentNameOutputOptions>[]): Promise<void>;
+export {};

package/dist/types/types/heading-levels.d.ts

@@ -1,2 +1,2 @@
 export declare const HEADING_LEVELS: readonly [1, 2, 3, 4, 5, 6];
-export type HeadingLevel = typeof HEADING_LEVELS[number];
+export type HeadingLevel = (typeof HEADING_LEVELS)[number];

package/dist/types/utils/environment.d.ts

@@ -1,2 +1,26 @@
-export declare const IS_SERVER: boolean;
+/**
+ * Environment detection helper
+ *
+ * Goal: Distinguish between real browser execution and Stencil's server-side
+ * hydration context. During SSR/hydration Stencil provides a mocked `window`
+ * (Domino / JSDOM–like) so naive checks (e.g. `typeof window !== 'undefined'`)
+ * incorrectly classify the environment as a browser.
+ *
+ * Detection strategy:
+ * - Stencils hydrate context uses a hardcoded user agent string ('MockNavigator')
+ *   and origin ('http://mockdoc.stenciljs.com') for its mocked `window` object.
+ *   We can use this to identify the hydrate context.
+ * - Stencils unit test context also uses the same hardcoded user agent string,
+ *   but a differnet value for the origin.
+ *   That's why comparing the origin is aboslutely mandatory.
+ * - Since we test the hydrate app in the test context, the origin is getting
+ *   overwritten by the test setup, leading to a false positive in the
+ *   `isHydrateApp` detection.
+ *   To circumvent this, we use a global flag (`isHydrateAppTestEnv`),
+ *   that we set/reset during the server test, so we can correctly identify
+ *   the hydrate app in the test context.
+ *   As a drawback, we can't properly test if the hydrate app is detected as
+ *   expected, in a real world scenario (elsewhere than in our tests).
+ */
 export declare const IS_BROWSER: boolean;
+export declare const IS_SERVER: boolean;

package/dist/types/utils/get-focusable-children.d.ts

@@ -1,2 +1,2 @@
-export declare function getFocusableChildren(element: Element): HTMLElement[];
-export declare function getDeepFocusableChildren(element: Element): HTMLElement[];
+export declare function getFocusableChildren(element: Element | Document | ShadowRoot): HTMLElement[];
+export declare function getDeepFocusableChildren(el: Element | DocumentFragment, filter?: (el: Element) => boolean, visited?: Set<Node>): HTMLElement[];

package/dist/types/utils/tests/environment/hydrate-app-helper.d.ts

@@ -0,0 +1,5 @@
+export declare function getAppEnv(): Promise<{
+    IS_BROWSER: boolean;
+    IS_SERVER: boolean;
+}>;
+export declare function afterTestCleanup(): void;

package/dist/types/utils/tests/environment/post-env-test.d.ts

@@ -0,0 +1,3 @@
+export declare class PostEnvTest {
+    render(): any;
+}