/* LanderUi custom elements bundle */

import { Components } from "../types/components";

interface LanderAnimate extends Components.LanderAnimate, HTMLElement {}
export const LanderAnimate: {
  prototype: LanderAnimate;
  new (): LanderAnimate;
};

interface LanderBlock extends Components.LanderBlock, HTMLElement {}
export const LanderBlock: {
  prototype: LanderBlock;
  new (): LanderBlock;
};

interface LanderButton extends Components.LanderButton, HTMLElement {}
export const LanderButton: {
  prototype: LanderButton;
  new (): LanderButton;
};

interface LanderColumn extends Components.LanderColumn, HTMLElement {}
export const LanderColumn: {
  prototype: LanderColumn;
  new (): LanderColumn;
};

interface LanderFooter extends Components.LanderFooter, HTMLElement {}
export const LanderFooter: {
  prototype: LanderFooter;
  new (): LanderFooter;
};

interface LanderHeader extends Components.LanderHeader, HTMLElement {}
export const LanderHeader: {
  prototype: LanderHeader;
  new (): LanderHeader;
};

interface LanderHeadline extends Components.LanderHeadline, HTMLElement {}
export const LanderHeadline: {
  prototype: LanderHeadline;
  new (): LanderHeadline;
};

interface LanderInput extends Components.LanderInput, HTMLElement {}
export const LanderInput: {
  prototype: LanderInput;
  new (): LanderInput;
};

interface LanderPage extends Components.LanderPage, HTMLElement {}
export const LanderPage: {
  prototype: LanderPage;
  new (): LanderPage;
};

interface LanderText extends Components.LanderText, HTMLElement {}
export const LanderText: {
  prototype: LanderText;
  new (): LanderText;
};

/**
 * Utility to define all custom elements within this package using the tag name provided in the component's source. 
 * When defining each custom element, it will also check it's safe to define by:
 *
 * 1. Ensuring the "customElements" registry is available in the global context (window).
 * 2. The component tag name is not already defined.
 *
 * Use the standard [customElements.define()](https://developer.mozilla.org/en-US/docs/Web/API/CustomElementRegistry/define) 
 * method instead to define custom elements individually, or to provide a different tag name.
 */
export declare const defineCustomElements: (opts?: any) => void;

/**
 * Used to manually set the base path where assets can be found.
 * If the script is used as "module", it's recommended to use "import.meta.url",
 * such as "setAssetPath(import.meta.url)". Other options include
 * "setAssetPath(document.currentScript.src)", or using a bundler's replace plugin to
 * dynamically set the path at build time, such as "setAssetPath(process.env.ASSET_PATH)".
 * But do note that this configuration depends on how your script is bundled, or lack of
 * bunding, and where your assets can be loaded from. Additionally custom bundling
 * will have to ensure the static assets are copied to its build directory.
 */
export declare const setAssetPath: (path: string) => void;

export * from '../types';