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 🙏

© 2026 – Pkg Stats / Ryan Hefner

ngml

v0.0.0

Published

Angular Markup Language

Readme

.ngml - Angular Markup Language

A more concise alternative to HTML, compatible with plain HTML and angular templates

Example

Here is an example in .html from the angular docs:

<!--html example-->
<h4>Tabs Demo</h4>
<ui-tabs>
  <template ui-pane title='Overview' active="true">
    You have {{details.length}} details.
  </template>
  <template *ngFor="#detail of details" ui-pane [title]="detail.title">
    {{detail.text}} <br><br>
    <button class="btn" (click)="removeDetail(detail)">Remove</button>
  </template>
  <template ui-pane title='Summary'>
    Next last ID is {{id}}.
  </template>
</ui-tabs>
<hr>
<button class="btn" (click)="addDetail()">Add Detail</button>

And here is the same example in .ngml

//ngml example
h4(Tabs Demo);
ui-tabs{
    template[ui-pane, title:Overview, active:true](You have {{details.length}} details.);
    template[ui-pane, *ngFor:#detail of details, @title:detail.title]({{detail.text}}){
        br;br;
        button.btn[&click:removeDetail(detail)](Remove);
    }
    template[ui-pane, title:Summary](Next last ID is {{id}}.);
}
hr;
button.btn[@click:addDetail()](Add Detail);

Benefits

  • ngml is more compact (~80% smaller) which makes it easier to type and refactor

  • the simplicity makes it easier to read the important parts without the clutter of closing tags and quotation marks

  • Syntax style is c-like, largely based on less/sass which makes it easier to learn.

  • Abstraction of html allows for customisation of output eg [title]="detail.title" vs bind-title="detail.title"

  • cleaner multiline attributes. In angular you often end up with lots of attributes on the same line, and trying to make that readable can be a nightmare. Taking a (rather verbose) example from Ionic 2's code (https://github.com/driftyco/ionic/blob/2.0/ionic/components/searchbar/searchbar.ts), which is more readable to you? Single Line HTML

    <input [value]="value" (input)="inputChanged($event)" (blur)="inputBlurred()" (focus)="inputFocused()" class="searchbar-input" type="search" [attr.placeholder]="placeholder" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false">

Formatted HTML

<input 
    [value]="value" 
    (input)="inputChanged($event)" 
    (blur)="inputBlurred()" 
    (focus)="inputFocused()" 
    class="searchbar-input" 
    type="search" 
    [attr.placeholder]="placeholder" 
    autocomplete="off" 
    autocorrect="off" 
    autocapitalize="off" 
    spellcheck="false">

ngml:

input.searchbar-input[
    @value:value 
    &input:inputChanged($event) 
    &blur:inputBlurred() 
    &focus:inputFocused() 
    class:searchbar-input 
    type:search 
    @attr.placeholder:placeholder 
    autocomplete:off 
    autocorrect:off 
    autocapitalize:off 
    spellcheck:false
];

Todo

  • Compiler
  • Gulp plugin
  • Webpack loader plugin
  • Sourcemapping
  • Online demo
  • Intellij syntax plugin
  • Sublime syntax plugin