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

@open-pioneer/integration

v2.4.0

Published

Provides techniques for the communication between an application (web component) and its embedding site.

Downloads

177

Readme

@open-pioneer/integration

This package provides techniques for the communication between an application (web component) and its embedding site. This is useful when the application's web component is embedded into another site.

The package exports the ApiExtension interface that can be used to provide API functions that can be called from the outer site to trigger actions in the web component. The ApiExtension support is implemented in the @open-pioneer/runtime package.

Additionally, the package contains the ExternalEventService, which can be used to emit events to the host site from inside the Open Pioneer Trails application.

Usage

Web component API

To provide API functions a service providing "integration.ApiExtension" needs to be implemented. The service must implement the ApiExtension interface with its getApiMethods() function. The functions returned by getApiMethods() will be available as methods on the web component's API.

For example:

// build.config.mjs
import { defineBuildConfig } from "@open-pioneer/build-support";

export default defineBuildConfig({
    services: {
        ExampleApiExtension: {
            provides: "integration.ApiExtension",
            ...
        },
        ...
    },
    ...
});
// TextApiExtension.ts
import { ServiceOptions } from "@open-pioneer/runtime";
import { ApiExtension } from "@open-pioneer/integration";

// implement ApiExtension interface
export class TextApiExtension implements ApiExtension {
    // returns a set of methods that will be added to the web component's API.
    async getApiMethods() {
        return {
            // exampleMethodName method is available
            exampleMethodName: (sampleParameter: string) => {
                // do something
            }
        };
    }
}

To use the API methods in the surrounding site, call the when() method on the app. It resolves to the app's API when the application has started. It is then possible to call the provided methods on the returned API instance.

For example:

<!doctype html>
<html lang="en">
    ...
    <body>
        <api-app id="app"></api-app>
        <script type="module" src="example-path/app.ts"></script>
    </body>
    <script>
        customElements.whenDefined("api-app").then(() => {
            const app = document.getElementById("app");
            app.when().then((api) => {
                api.exampleMethodName("Example string");
            });
        });
    </script>
</html>

Note: The when() method is implemented as a method on the custom element class generated by the createCustomElement() function in the runtime package. It is available once the web component is defined (which is why the example code waits by calling customElements.whenDefined).

ExternalEventService

In your UI or one of your services, reference the "integration.ExternalEventService" interface to obtain an instance of the ExternalEventService. For example:

// build.config.mjs
export default defineBuildConfig({
    services: {
        YourService: {
            references: {
                eventService: "integration.ExternalEventService"
            }
        }
    }
});

Then, call emitEvent on the service to emit an event:

// Emits a new custom event from the web component.
//
// The second parameter supports arbitrary payloads.
// It will be transported in the CustomEvent's `detail` property.
//
// See also https://developer.mozilla.org/en-US/docs/Web/API/CustomEvent/detail
eventService.emitEvent("extent-selected", {
    extent: ...
});

// You can also emit your own event instances (subclasses of the browser's Event class etc.)
eventService.emitEvent(new CustomEvent(...));

The events are emitted on the application's host node. You can subscribe to them from outside the application via addEventListener:

/* If the html looks like this:
    <html>
        <body>
            <my-pioneer-app id="app"></my-pioneer-app>
        </body>
    </html>
*/
const app = document.getElementById("app");
app.addEventListener("extent-selected", (event) => {
    console.log("Selected extent:", event.detail.extent);
});

License

Apache-2.0 (see LICENSE file)