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

htmlbars

v0.14.24

Published

HTMLBars compiles Handlebars templates into document fragments rather than string buffers

Downloads

2,907

Readme

Status Build Status Sauce Test Status

HTMLBars is a layer built on top of the Handlebars template compiler.

Goals

The goal of HTMLBars is to have a compiler for Handlebars that builds a DOM rather than a String.

This means that helpers can have special behavior based on their context (they know if they are inside an <a> tag, inside an attribute, etc.)

Ultimately, the goal is to have a good data binding setup for Handlebars that can work directly against DOM nodes and doesn't need special tags in the String for the data binding code to work (a major limitation in Ember).

There are also many performance gains in HTMLBars' approach to building DOM vs the HTML-unaware string building approach of Handlebars.

Security

HTMLBars aims to not only ease interacting with data-bound templates, but also to provide it in a secure-by-default way. Thanks to the design of HTMLBars it has both handlebars and HTML awareness, this allows for best practices by default. For example:

<div>{{fullName}}</div>

ultimately becomes:

var div = document.createElement('div');
div.textContent = fullName; // when fullName changes

In this example, HTMLBars is aware that values set to textContent on a div is treated by the browser as inert text. In other words, in this scenario HTMLBars knows the content is safe, and no escaping is required.

HTML has many interesting contexts, in each HTMLBars aims to do the right thing. This may be, using the correct browser API, sanitizing, or disabling a feature entirely.

Needless to say, we take security very seriously. If there is something we missed, please report via the Ember.js responsible security disclosure system.

Usage

TODO: much change. This section will be updated shortly.

Until then, check out ARCHITECTURE.md for info on how HTMLBars is structured and its approach to efficiently building / emitting DOM.

Building HTMLBars

  1. Ensure that Node.js is installed.
  2. Run npm install to ensure the required dependencies are installed.
  3. Run npm run-script build to build HTMLBars. The builds will be placed in the dist/ directory.

How to Run Tests

Via Ember CLI

  1. Run: ember test --server

Ember CLI is a CI tool, so it will run tests as you change files.

On the console with PhantomJS

  1. Run npm test.

In a browser

  1. Run npm start.
  2. Visit http://localhost:4200/tests/.