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

ef-runtime-client

v1.2.7

Published

A runtime library designed to help host apps initialise the runtime on the client-side and dynamically load components from an external component registry.

Downloads

141

Readme

Extensible Frontends Runtime Client

A runtime library designed to help host apps initialise the runtime on the client-side and dynamically load components from an external component registry.

Table of Contents

About

This client-side runtime library is part of the Extensible Frontends project. It enables host applications to initialise a runtime environment that can dynamically load and manage components from an external component registry.

Getting Started

Prerequisites

  • Node.js
  • npm or yarn

Installation

Install the package using npm or yarn:

npm install ef-runtime-client

Usage

Initialisation

To initialise the runtime, provide the system code for your host application:

import * as EFRuntime from "ef-runtime-client";

EFRuntime.init({ systemCode: "ef-demo-host" });

If needed, you can override specific entries in the component registry. Specify separate URLs for JavaScript and CSS like so:

EFRuntime.init({
  systemCode: "ef-demo-host",
  overrides: {
    "my-component": {
      js: "http://localhost:3000/my-component.js",
      css: "http://localhost:3000/my-component.css",
    },
  },
});

Using the Extensible Frontends Overrides UI

Instead of modifing the init function in the page's code, you can use the Extensible-Frontends override UI to test your component locally. To do so, You can add the key efui to your browser's localStorage manually and set its value to "true" or by running the following command in your browser's console:

localStorage.setItem("efui", "true")

If the EFUI button is showing in the page you are developing and you would like to disable it, simple remove the key from your browser's localStorage manually or by running the following command in your browser's console:

localStorage.removeItem("efui")

Custom Logging

The runtime allows you to implement custom logging. You can utilize this feature to integrate your own logging system or to assist in debugging. Pass a logging object during initialisation with custom functions for info, warn, error, and debug.

Here's an example:

EFRuntime.init({
  systemCode: "ef-demo-host",
  logging: {
    info: (message, ...args) => customLogger.info(message, ...args),
    warn: (message, ...args) => customLogger.warn(message, ...args),
    error: (message, ...args) => customLogger.error(message, ...args),
    debug: (message, ...args) => customLogger.debug(message, ...args),
  },
});

If you do not provide specific functions, default console methods are used for errors, and other logs are suppressed.

Running Tests

Execute the test suite with the following command:

npm test

FAQ