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 🙏

© 2026 – Pkg Stats / Ryan Hefner

lit-service-status-component

v0.0.3

Published

Service status component built with lit

Downloads

11

Readme

lit-service-status-component

This is a web component built with Lit that reveals the status of a service.

The component provides a simple overview of the availability of the service. This by querying the health check of the service.

The following properties of the component are adjustable:

Properties

| Property | Attribute | Description | Type | Default | | ------------------------- | --------------- | ----------- | -------- | ----------- | | apiToCheck (required) | api-to-check | | string | undefined | | offlineColor | offline-color | | string | 'red' | | offlineText | offline-text | | string | 'Offline' | | onlineColor | online-color | | string | 'green' | | onlineText | online-text | | string | 'Online' | | status | status | | string | undefined |


Getting Started

To use the component, first install this package

npm i lit-service-status-component

Then you add the component in your HTML page and reference the script. Change the necessary attributes as you wish.

    <!DOCTYPE html>
    <html lang="en">
    <head>
        <meta charset="UTF-8">
        <meta http-equiv="X-UA-Compatible" content="IE=edge">
        <meta name="viewport" content="width=device-width, initial-scale=1.0">
        <title>Test</title>
        <script type="module" src="/node_modules/d09-service-status/dist/d09-service-status/d09-service-status.esm.js"></script>
    </head>
    <body>
        <d09-service-status-component
        api-to-check="https://apidgdv.gent.be/supporting/communication-platform-core/v1/status/am-i-up" 
        online-text="Up"
        offline-text="Down" 
        online-color="#BDD68D"
        offline-color="#E89393"     
        ></d09-service-status-component>    
    </body>
    </html>

Production & Development

There are a number of points of attention when using lit elements read : https://lit.dev/docs/tools/development/ The component was tested with the web dev server approach :

Local dev servers Permalink to “Local dev servers”# Lit is packaged as JavaScript modules, and it uses bare module specifiers that are not yet natively supported in most browsers. Bare specifiers are commonly used, and you may want to use them in your own code as well. For example:

import {LitElement, html, css} from 'lit';

To run this code in the browser, the bare specifier ('lit') needs to be transformed to a URL that the browser can load (such as '/node_modules/lit/lit.js').

There are many development servers that can deal with module specifiers. If you already have a dev server that does this and integrates with your build process, that should be sufficient.

If you need a dev server, we recommend Web Dev Server.