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

noodles

v0.2.0

Published

High Performance templating language

Downloads

14

Readme

Noodles Templating System

###Created by Nathan Sweet Introduction

Noodles is a high-performance template language written in JavaScript. It is written using requirejs, so it can be used both on the server and on the client. It is platform agnostic so that it may be as a portable as possible.

Noodles is relatively compact and could be used to on the front end to render templates that have a little too much logic in them, to allow native JavaScript to control their logic in a readable way. Or it could be used as part of a client MVC to minimize refactoring code in the transfer of "Views" from the server to the client (and visa versa).

The language goals of Noodles syntax are to be as permissive, readable, and colloquial as possible. The language is written so that the server of the template should not be adversely affected by a poorly written template. The templating engine won't break over mistakes and will gloss over them as best as possible, while still providing a warning system that can be viewed if the writer of the template wishes.

Performance

It's performance is more than a little impressive. Compile time, though usually not important, is still quite fast (usually less than 20 milliseconds). Medial string values between data access affect performance quite negligibly, so if you have a large template, but with little logic, you can rest assured that you will have just as fast performance if you had a minimal amount of text. As for rendering time: on node, a template which has to do object access about 100 times (more than the average template will probably have) sees some impressive speed. Here is a sample run (see tests/node-test.js):

The mean time was:  1586.0815 μs (1.5 milliseconds).
The median time was: 1538 μs (1.5 milliseconds).
The upper bound time was:  16943 μs (16 milliseconds).
The lower bound time was:  1500 μs(1.5 milliseconds).
The standard deviation was: 1673.9541218916183 μs (1.6 milliseconds).
The number of runs was:  10,000.

On templates that see more typical object access (sub 50 iterations) the times can be as low as 100 microseconds. Singular object access seems to take about 10-20 microseconds. These times will most likely be an improvement on most templating systems, and will certainly never be an issue on the client.