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

seo-lite

v0.1.1

Published

Tiny SEO helper for vanilla JS + SSR

Readme

SEO-lite

⚡️ Tiny SEO helper for vanilla JS + SSR

SEO-lite is a dependency-free helper for managing SEO tags both on the client and server side.


✨ Features

  • 🧑‍💻 Client: Set <title> and <meta> tags directly in the DOM
  • 🖥 Server: Generate SEO tag strings for SSR/templates
  • 🌲 Treeshaking: Import only what you need—client or server
  • ⚡️ Zero dependencies: Lightweight and portable
  • 🟦 TypeScript support: Full typings and autocompletion
  • 🏷️ Open Graph autocomplete: Common OG meta attributes included

🚀 Getting Started

1. Install

npm install seo-lite
# or
yarn add seo-lite

2. Import

Client-side

import { setSeo, cleanUp } from 'seo-lite/client'

Server side

import { generateSeoString } from 'seo-lite/server'

Universal

import { setSeo, cleanUp, generateSeoString } from 'seo-lite'

CommonJS:

const { generateSeoString } = require('seo-lite/server')

3. API Overview

All functions use a shared schema for SEO tags:

Schema:

{
    title: string,
    "og:description": string,
    customMetaTagName: string,
    multipleAttributesTag: [
      {
        attributes: [
          {
            attributeName: string,
            attributeValue: string,
          },
          {
            attributeName: string,
            attributeValue: string,
          }
        ]
      }
    ]
  }

Where is:
title - Page title
og:description - Open Graph or any custom meta name
customMetaTagName - Any custom meta tag
multipleAttributesTag - Array of meta tags, each with any attributes

Example for multiple meta attributes:

multipleAttributesTag: [
      {
        attributes: [ // array of tag attributes
          {
            attributeName: 'attribute_name_1', // tag name
            attributeValue: 'attribute value', // tag value
          },
          {
            attributeName: 'attribute_name_2',
            attributeValue: 'attribute value',
          }
        ]

Functions

1. cleanUp()
cleanUp(schema)
Removes tags matching the schema from the DOM.
2. setSeo()
setSeo(schema, { isAutoClean: boolean })
Sets SEO tags in the DOM. If isAutoClean is true (by default), previous tags described in schema are removed via cleanUp().
3. generateSeoString()
generateSeoString(schema, { isPretty: boolean })
Generates a string of HTML tags for SSR use.
When isPretty is true (by default), tags are separated by newlines (\n).