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

@alizain/coconut

v0.2.4

Published

static site generator with proper data model and react templates

Downloads

11

Readme

Coconut

A simple React & fsdb based static site generator.

Check out the sample directory for a simple example.

Data/Content Files

The two currently supported formats are:

  • Markdown
  • YAML
  • JSON

For md files, front-matter is treated as root level data, and all content is inside the data key

---
title: The Obliteration of Man
---

I am God

Which gets compiled to

{
  title: "The Obliteration of Man",
  body: "\nI am God",
  parent: ...
}

Layouts

The entire layouts folder is required on startup. From there, all registered components are called with their respective nodes and rendered (ie. all nodes with type: book get rendered by the following React component)

layouts/Book.js

import { Registry } from "@alizain/coconut"

function Book({ node }) {
  return (
    <h1>{node.title}</h1>
  )
}

Registry.set("book", Book)

You can also set a default layout to use for nodes:

Registry.setDefault(Page)

Node layout is determined by the layout property, then by the type property. So a node with the following keys, will be rendered using the listing renderer.

{
  layout: "listing",
  type: "collection"
}

Config

{
  dataDir: "./data",         // content/data directory
  layoutDir: "./layouts",    // React component directory
  distDir: "./dist",         // compiled HTML output directory
  commonFile: "common"       // shared props file
}