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

ilc-plugins-sdk

v2.1.0

Published

This package provides interfaces & base classes for ILC plugins developers

Downloads

100

Readme

SDK for ILC plugins development

NPM package NPM downloads

SDK intended for use by developers that build plugins for Isomorphic Layout Composer.

Installation

$ npm i ilc-plugins-sdk

Plugins naming convention

In order to be discoverable by ILC plugin manager - NPM package that contains plugin should be named in one of the following ways:

  • ilc-plugin-* Example: ilc-plugin-myreporting
  • @*/ilc-plugin-* Example: @myorg/ilc-plugin-myreporting

Installation of the plugin

In order to use ILC with installed plugins we recommend extending base Docker image in the following way:

ARG ilc_version=latest
FROM namecheap/ilc:${ilc_version}

RUN npm i ilc-plugin-yourpluginname

# Need to rebuild ILC if your plugin has browser implementation
RUN npm run build

Supported plugin types

Server side plugins

Plugins of this type should provide single entry point for the server implementation. It will be detected via main property in your package.json.

Reporting plugin

Should implement IlcReportingPlugin interface. Allows customizing logs output of the ILC container and optionally set custom behaviour for request ID generation & handling.

I18n params detection plugin

Should implement I18nParamsDetectionPlugin interface.

Isomorphic plugins

Plugins of this type should provide 2 entry points, for the server & browser side respectively. Server side entrypoint will be detected via main property in your package.json. While entrypoint for a browser side implementation expected to be in browser.js file in the root folder of NPM package.

Same approach should be used to fetch necessary interfaces for the server & browser side implementation:

Server side:

import { TransitionHooksPlugin } from 'ilc-plugins-sdk';

Browser side:

import { TransitionHooksPlugin } from 'ilc-plugins-sdk/browser';

Transition hooks plugin

Allows to set up route change hooks which may:

  • Prevent routing & display some UI.
  • Perform the redirect to another page.
  • Allow route change.

Should implement TransitionHooksPlugin interface for the browser & server side.