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

pikasu

v0.1.3

Published

Micro framework for preact

Readme

Pikasu

Micro framework for preact, which enables partial hydrating

Installation

npm i pikasu preact
yarn add pikasu preact
pnpm add pikasu preact

Usage

// file: pikasu.config.ts
import { defineConfig } from 'pikasu'

export default defineConfig({
  // ...
})

npm run pikasu

node dist/server/entry.mjs after building to launch the server

Overview

The pages/ directory acting like routes:

  • pages/index.tsx -> /
  • pages/some/path.tsx -> /some/path
  • pages/foo/index.tsx -> /foo
  • pages/_path/excluded.tsx -> <none>
  • routes/(group)/foo.tsx -> /foo
  • pages/[group]-[page]/[[id]].tsx -> /:group-:page/:id?
  • pages/bar/[...path].tsx -> /bar/**:path
import type { PageContext } from 'pikasu'

export default function Page(ctx: PageContext) {
  const { foo, bar } = ctx.params
}

All components are static by default. To make the component dynamic, add the client-load attribute:

return (
  // props will be JSON.stringify'ed, so only primitive values allows
  <DynamicComponent client-load foo="bar" />
)

The output of page will send to client as is, so define layout with html structure:

// file: layouts/DefaultLayout.tsx
import type { PropsWithChildren } from 'preact/compat'

export default function DefaultLayout({ children }: PropsWithChildren) {
  return (
    <html lang="en">
      <head>
        <meta charset="UTF-8" />
        <meta name="viewport" content="width=device-width, initial-scale=1.0" />
        <title>Website</title>
      </head>
      <body>
        <main>{children}</main>
      </body>
    </html>
  )
}
// file: pages/index.tsx
import DefaultLayout from '~/layouts/DefaultLayout.tsx'

export default function MainPage() {
  return (
    <DefaultLayout>
      <p>Hello world!</p>
    </DefaultLayout>
  )
}

Pages can also be async:

export default async function Page() {
  const data = await fetchSomeData()

  // doing somewhat with data
  return <Layout>...</Layout>
}