npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@humany/widget-types-floating

v1.0.58

Published

Type definition for Humany Floating widget.

Downloads

32

Readme

Humany Floating widget

The Floating widget consists of a trigger element (triggerDOMElement) and a main widget element (widgetDOMElement).

General commands

The following commands are part of the Webprovisions widget definition and are available for all widget types.

initialize(): Promise

No custom behaviour.

activate([options: BotWidgetActivationOptions]): Promise

Creates new instances of triggerDOMElement and widgetDOMElement. The triggerDOMElement is directly appended to the DOM whereas the widgetDOMElement is not appended until later.

After activation, the elements are available on the Container:

const widgetDOMElement = container.get('widgetDOMElement');
const triggerDOMElement = container.get('triggerDOMElement');

destroy(): Promise

Invokes moveOutsideViewport() and then removes widgetDOMElement and triggerDOMElement.

Widget commands

Regular commands can be invoked after the widget has been activated.

navigate(commands: { route: string, params?: { [key: string]: any }}): void

Navigates the widget to specified route with optional params.

moveInsideViewport(): void

Positions the widgetDOMElement inside the viewport relative to the triggerDOMElement. Together with CSS transitions this will create an animation where the widget is sliding in.

moveOutsideViewport(): void

Positions the widgetDOMElement outside the viewport relative to the triggerDOMElement. Together with CSS transitions this will create an animation where the widget is sliding out.

Services

Both asynchronous and synchronous services are available on the Container:

Async services:

// ES stage 3 syntax
const theService = await container.getAsync('theService');

// ES6 syntax
container.getAsync('theService').then((theService) => {

});

Sync services:

const theService = container.get('theService');

The following service is registered when a Floating widget is created.

Accessing the controller from a Plugin

The widget controller is available on initialize() (but not in the constructor). When extending from the Webprovisions.Platform.Plugin class, the controller is accessible on this.controller. Use the invoke() function to invoke commands on the widget API:

import { Plugin } from '@humany/widget-core';

class MyPlugin extends Plugin {
  initialize() {
    this.controller.invoke('[commandName]');
  }
}

See the Skeleton Plugin repository for an example on how to author a Webprovisions plugin.