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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@vimlet/meta

v3.0.3

Published

<p align="center"> <img src="https://vimlet.com/resources/img/Meta-txt.png" title="Vimlet Meta" alt="Vimlet Meta" height="150"> </p>

Readme

npm Travis (.org) branch Codacy grade GitHub

It is a tool that generate files from templates.

Features

  • Data binding.
  • Inheritance templates.
  • Glob patters to search for template files.
  • Watcher to look for changes and update files on the fly.

You can access the source code at vimlet/meta

Installation

npm install @vimlet/meta

Usage

  • meta.parse(template, options, callback);

    Returns the result of given template.

  • meta.parseTemplate(template, options, callback);

    Returns the result of given template file.

  • meta.parseTemplateGlob(include, options, callback);

    Returns an object with the result. {"relativePath":"", "result":""}

  • meta.parseTemplateGlobAndWrite(include, output, options, callback);

    Write the results to output folder while keeping files structure.

  • meta.watch(include, output, options);

    Do parseTemplateGlobAndWrite and keep looking for changes.

    options

    { "exclude": "glob patterns", "data": {}, "clean": false }

    • exclude: Used to skip files that you don't want to parse.
    • output: Directory where files will be written using parseTemplateGlobAndWrite.
    • data: Data to be bind.
    • clean: Empty output directory before parse.

Command mode:

  • vimlet-meta -i include -o output -e exclude -d data -c clean

    Calls meta.parseTemplateGlobAndWrite

  • vimlet-meta -i include -o output -e exclude -d data -c clean -w

    Calls meta.watch

Extra

vimlet-meta remove comments if there are only meta code within it.

<% teamplate("anothertemplate.vmi")%>

produce the same result as

// <% teamplate("anothertemplate.vmi")%>

or

/* <% teamplate("anothertemplate.vmi")%> */

This behaviour can be avoided using -p.

Example

  • Template: Hello I'm a template <%echo("Raw text");%>

  • Result: `Hello I'm a template Raw text

  • Template: Hello I'm a template <% data.name %>

  • Data: {"name":"vimlet-meta"}

  • Result: Hello I'm a template vimlet-meta

  • Template1: Hello I'm a template <%template(template2.vmi)%>

  • Template2: I'm another template

  • Result: Hello I'm a template I'm another template

Data binding

One of the meta advantages is the ability to bind data from a json. IE:

Template:

Hello <%= data.name%>

Data:

{"name": "Peter"}

Result:

Hello Peter

File extension

We use .vmt for vimlet meta templates and .vmi for vimlet meta imported in our imported templates but any extension is welcome.

Note that meta respects file extension if it is included in template name:

  • index.html.vmt after parsed will be written as index.html.

License

vimlet-meta is released under MIT License. See LICENSE for details.