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

edge-template-engine

v1.0.7

Published

Fast and simple template-engine for Edge Functions

Downloads

3

Readme

Edge Template Engine

The problem

Edge functions (Vercel, Netlify, Cloudflare Workers) are a great way to serve your code close to your end users. However, with edge functions you lose access to the file system, making it harder to use traditional template engines. Edge Template works around this issue by compiling your templates to native ES-modules. After compilation, you can just import your templates into any Edge function.

Universal rendering

Because ES-modules are compatible with any javascript environment, you can use the same template for sever-side rendering, pre-rendering, edge rendering ánd client-side rendering. This makes them truly isomorphic.

How to use

  1. first (pre)compile you template to esm. Typically you'd do this during your build step:
import edge from "edge-template-engine"
import * as fs from "fs"

// compile
let compiled = await edge.compile("<h1>${data.title}</h1>", "esm"); // or 'str' to render to string

// save the file to disk, so you can import it in the next step
fs.writeFileSync("./test.mjs", compiled, "utf8");
  1. Now you can import the template, and render it with the data:
import template from "./test.mjs"

const data = {
    "title":"Hello Edge!"
}
var result = template(data);

Template Syntax

echo

${data.something}

if exists

$(data.something?){<b>${data.something}</b>}

if doesn't exist

$(!data.something?){<b>Empty</b>}

loops/foreach

$(data.names:name){<b>I'm ${name}</b>}

if equals

${data.title == 'Hello Edge!' ? 'The condition is true' : 'The condition is false'}

any valid javascript expression

Inside ${} you can use any javascript expression you want. Functions, methods, properties, process.env...

Credits

Based on on li-template by Patrick Pissurno.

Press the :star: button

Don't forget to press the :star: button to let me know I should continue improving this project.