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

walrus

v0.10.1

Published

A bolder kind of mustache.

Downloads

1,523

Readme

Walrus

Build Status

Goal

  • Write a mustache templating language that fits more with the idea of view-objects as opposed to view-helpers

  • Support method helpers fully. This means:

    • (Semi)-Automatic invocation.
    • "Write what you mean" when it comes to functions.
    • Multiple arguments
    • Arguments may be primitive types
    • Ability to add in custom domain methods at the view object level (how do we do this?)
    • Still support helper methods and block helpers, but put the helper methods where they make the most sense
  • Support object paths like handlebars does

  • Make it easy to traverse back up to root, and to read as such

  • More to come...

Ideas

  • @ means this, like in coffeescript. This makes it easy to reference the root object context from anywhere.
  • do/end style blocks make more sense than # and / to me

Filter Packages

  • walrus.string: capitalization, casing, hyphenization, etc
  • walrus.inflection: pluralization, etc
  • walrus.date: date formatting
  • walrus.domain: bring raw json objects into the client domain (perhaps theres a better name for this)