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

@yamato-daiwa/handlebars-extensions

v0.0.0

Published

Helpers for the Handlebars template engine.

Downloads

20

Readme

Yamato Daiwa Handlebars Extensions

Some helpers for the Handlebars template engine.

Usage

Each helper function of this package has been wrapped by the object. Most of these objects has single key/value pair where the key is the name of the helper function and the value is the helper function itself. For example, areStringsEqual helper function has been wrapped to AreStringsEqualHandlebarsHelper object, where the areStringsEqual is the key. To register the helpers such this one, use the spread operator:

import { create as initializeHandlebarsTemplateEngine } from "express-handlebars";
import { 
  AreStringsEqualHandlebarsHelper,
  IsEmptyObjectHandlebarsHelper,
  IsNonEmptyObjectHandlebarsHelper
} from "@yamato-daiwa/handlebars-extensions";

const handlebarsTemplateEngine = initializeHandlebarsTemplateEngine({
  helpers: {
    ...AreStringsEqualHandlebarsHelper,
    ...IsEmptyObjectHandlebarsHelper,
    ...IsNonEmptyObjectHandlebarsHelper
  }
});

Why it is impossible to export just the function itself without object wrapper?

Because if to export, for example, the areStringsEquals as

export { areStringsEquals } from "@yamato-daiwa/handlebars-extensions"

it is unclear outside the Handlebars files that areStringsEquals is the helper function indented to be used in the Handlebars, not the common function which could be safely used in normal TypeScript/JavaScript.

Functionality

AreStringsEqualHandlebarsHelper / areStringsEqual

{{#areStringsEqual familyName givenName}}

  <p>The family name is even with given name?!</p>
    
{{/areStringsEqual}}

IsEmptyObjectHandlebarsHelper / isEmptyObject

{{#isEmptyObject socialNetworkProfilesURIs}}

  <p>No social networks profiles registered</p>
    
{{/isEmptyObject}}

IsNonEmptyObjectHandlebarsHelper / isNonEmptyObject

<dl>
    
  <dt>Full Name</dt>
  <dd>{{ fullName }}</dd>
    
  {{#isNonEmptyObject socialNetworkProfilesURIs}}
    <dt>Social networks</dt>
    <dd>
      <ul>
           
        {{#each socialNetworkProfilesURIs}}
           
          <li>
              
            {{#areStringsEqual @key "facebook"}}
              <a href="{{ this }}">
                <svg>
                  <!-- The SVG code of teh Facebook icon ... -->
                </svg>
              </a>
            {{/areStringsEqual}}
                 
            {{#areStringsEqual @key "instagram"}}
             <a href="{{ this }}">
              <svg>
                <!-- The SVG code of teh Instagram icon ...-->
              </svg>
             </a>
            {{/areStringsEqual}}
              
            {{#areStringsEqual @key "twitter"}}
              <a href="{{ this }}">
                <svg>
                  <!-- The SVG code of teh Twitter icon ...-->
                </svg>
              </a>
            {{/areStringsEqual}}
              
          </li>
        
        {{/each}}
          
      </ul>
        
    </dd>
  {{/isNonEmptyObject}}
    
</dl>