@everymatrix/nuts-inbox-widget 0.0.10 → 1.45.5

package/dist/components/index.d.ts

@@ -1,26 +0,0 @@
-/* NutsInboxWidget custom elements */
-
-import type { Components, JSX } from "../types/components";
-
-/**
- * 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
- * bundling, 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 interface SetPlatformOptions {
-  raf?: (c: FrameRequestCallback) => number;
-  ael?: (el: EventTarget, eventName: string, listener: EventListenerOrEventListenerObject, options: boolean | AddEventListenerOptions) => void;
-  rel?: (el: EventTarget, eventName: string, listener: EventListenerOrEventListenerObject, options: boolean | AddEventListenerOptions) => void;
-}
-export declare const setPlatformOptions: (opts: SetPlatformOptions) => void;
-
-export type { Components, JSX };
-
-export * from '../types';

package/dist/components/index.js

@@ -1 +0,0 @@
-export { setAssetPath, setPlatformOptions } from '@stencil/core/internal/client';

package/dist/components/nuts-inbox-widget.d.ts

@@ -1,11 +0,0 @@
-import type { Components, JSX } from "../types/components";
-
-interface NutsInboxWidget extends Components.NutsInboxWidget, HTMLElement {}
-export const NutsInboxWidget: {
-  prototype: NutsInboxWidget;
-  new (): NutsInboxWidget;
-};
-/**
- * Used to define this component and all nested components recursively.
- */
-export const defineCustomElement: () => void;