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 🙏

© 2025 – Pkg Stats / Ryan Hefner

homegrownjs

v0.1.5

Published

super simple and fast ts frontend framework

Downloads

4

Readme

homegrown

A stupidly simple frontend framework with ssr support

(I did write better documentation but I lost it somehow...)

Setup

Install node module:

npm install homegrownjs

To setup the backend with ssr, I would reccomend using the go backend which has all the processing setup. Use the code in the main.go file in the example project: homegrown-homepage. It would proably be easier to clone the project and then edit the files in the pages/root to follow along with the simple tutorial.

Tutorial

Each component is simply a function that returns an html component:

export function TestComponent(props: hg.Props, ctx hg.Ctx) {
    return `
        here be dragons
    `

}

Use Props

Simply access the props map as you would for any other js map:

export async function TestComponent(props: hg.Props, ctx: hg.Ctx) {
    return `
        here be dragons and ${props.get("propName")}
    `
}

Hydrate promises on resolve

To hydrate the piece of the page once the promise has resolved we use the hg.hydr function:

function sleep(time: number) {
    return new Promise<null>((resolve, reject)=>{setTimeout(()=>{resolve(null)}, time)})
}

var fetchPost = async () => {
        await sleep(5000) // simulate doing some processing
        return fetch("https://jsonplaceholder.typicode.com/posts/1").then((val: Response) => val.text())
    }


export async function TestComponent(props: hg.Props, ctx: hg.Ctx) {
    return `
        here be dragons and ${props.get("name")}
        ${await hg.hydr(
            "This is from the server. Hello!",
            fetchPost(), "componentNameGoesHere", ctx
        )}
    `
}