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

@js-template-engine/core

v2.0.0

Published

Template engine core: processes data-defined component templates into HTML, CSS, and JavaScript

Readme

@js-template-engine/core

The template engine core. Processes components defined as plain, typed data into working HTML, CSS, and JavaScript — no extensions required — and delegates to framework extensions for other targets.

import { process } from '@js-template-engine/core';
import { defineTemplate } from '@js-template-engine/types';

const template = defineTemplate({
  type: 'component',
  name: 'Button',
  children: [
    {
      type: 'element',
      tag: 'button',
      attributes: { class: ['button'], type: 'button' },
      events: [{ name: 'click', handler: 'handleClick' }],
      children: [{ type: 'text', content: 'Save' }],
    },
  ],
});

const result = process(template);
// result.files → [{ path: 'Button.html', content: '...' }]

HTML output

HTML output is a static rendering: a zero-dependency preview and the semantic baseline for every framework target. Dynamic concepts render as static previews — expressions become {{ expression }} placeholders, conditionals render every branch between <!-- if --> comments, iterations render their children once between <!-- for --> comments, and slots render their fallback content.

Output strategies

Styles and scripts share one strategy vocabulary, configured independently through options.styling and options.scripting:

| Strategy | Styles | Scripts | |---|---|---| | inline | style="..." attributes | onclick="..." attributes | | in-file (default) | a <style> block | a <script> block | | separate-file | Button.css + link | Button.js + script tag |

Validation

process() validates the template first and throws a TemplateError carrying a node path (such as children[2].conditions[0]) on the first structural violation. validateTemplate is exported for standalone use.

Extensions

Extensions are passed directly — no registry, no string-key lookup:

process(template, { extensions: [react(), bem()] });

Framework extensions implement the FrameworkExtension interface exported from this package and take over rendering entirely; the core stays free of framework knowledge.