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

expand-template-literal

v1.0.3

Published

Expand template literals supplied as strings.

Downloads

20

Readme

expand-template-literal

Expands template literals supplied as strings.

The purpose is to provide the most powerful and comfy templating experience in places where templates can be trusted. DO NOT use where malicious templates could cause harm.

Templates work exactly as JavaScript template literals, because they are. Passed strings are just wrapped in a context configuring expression, and passed to eval().

Pros:

  • The power of JavaScript template literals with variables and embedded expressions in your templates.
  • Apart of serializable data, templates can also use utility functions and constructors.
  • Tiny, less than 300 bytes.

Cons:

  • Absolutely insecure.
  • Templates can do anything the context they run in can.
  • Can't be used in places where templates can't be trusted.

Install

npm install expand-template-literal

Usage

import {expandTemplateLiteral as expand} from 'expand-template-literal';
import * as dayjs from 'dayjs';

const result = expand("${name} arrived at ${dayjs(arrival).format('dddd')}.", {
	// Provide templates with variables
	name: 'John',
	arrival: 1636377526618,

	// And even utilities they can use
	dayjs,
});

console.log(result); // "John arrived at Monday."

API

Exported interfaces:


expandTemplateLiteral

function expandTemplateLiteral(template: string, variables?: Record<string, any>): string;

Expands passed template with variables supplied by 2nd argument.

template

Type: string required

JavaScript template literal string.

variables

Type: Record<string, any> optional

Values can be literally anything. Serializable data, functions, constructors, instances, symbols, ...

Return

Returns expanded template as a string, or throws TemplateError if anything inside the template went wrong.


TemplateError

Thrown when template errors out. Nothing special, just a custom constructor to identify the error with.