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

happy-little-trees

v1.0.0-beta.20

Published

A style guide with auto-generating code samples and on-page nav.

Downloads

72

Readme

Happy Little Trees is a style guide with auto-generating code samples and on-page nav.

Currently, HLT has some pretty strict requirements that mesh well with our workflow. We may make it more customizable if demand arises.

Installation

npm i -S vue
npm i -D happy-little-trees

If you don't use Vue in your project, you can save it as a dev dependency instead.

Usage

Create a JavaScript file with the following contents and include it in your document:

import hlt from 'happy-little-trees';
import Vue from 'vue';

window.vm = new Vue(hlt);

hlt is an object prepped for a Vue instance. If you need to change/add anything, do so like this:

import HexTabs from 'vue-hex-tabs';
import hlt     from 'happy-little-trees';
import Vue     from 'vue';

hlt.components = {
  HexTabs:         HexTabs.HexTabs,
  HexTabList:      HexTabs.HexTabList,
  HexTab:          HexTabs.HexTab,
  HexTabPanelList: HexTabs.HexTabPanelList,
  HexTabPanel:     HexTabs.HexTabPanel,
};

hlt.data = {...};

window.vm = new Vue(hlt);

Note: When generating code samples, HLT checks for Hex components. If any are found, it'll use Hex Tabs to display the code. One tab for the Vue component markup, and one for the rendered Vue component (standard HTML). If you have your own components, make sure to include Hex Tabs in there as shown above.

Markup

In order for HLT to work, your markup will need to look something like this:

<header class="header-primary">
  <nav>
    <a href="/style-guide" class="logo">Style Guide</a>
    <ol>
      <li><a href="some-page">Some Page</a></li>
      <li><a href="kitchen-sink">Kitchen Sink</a></li>
    </ol>
  </nav>
</header>

<main>
  <section>
    <h2>Typography</h2>
    <h3>Headings</h3>
    <div class="sample">
      <h1>Heading 1</h1>
      <h2>Heading 2</h2>
      <h3>Heading 3</h3>
      <h4>Heading 4</h4>
      <h5>Heading 5</h5>
      <h6>Heading 6</h6>
    </div>

    <h3>Body text</h3>
    <div class="sample">
      <p>
        Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt
        ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco
        laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in
        voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat
        cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
      </p>
    </div>
  </section>
</main>
  1. Anything you want an auto-generated code sample for must be in a .sample.
  2. The nav is generated from all direct descendant headings in main > section. So in the above markup, "Typography," "Headings," and "Body Text" will end up in the nav, but "Heading 1" through "Heading 6" will not.
  3. You need an element with the class header-primary. Once you scroll past it, the generated sidebar nav will have the class is-sticky applied to it. Which you can use to set position: fixed for a sticky nav.