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

@static-pages/twig

v2.0.0-alpha.1

Published

Twig template engine bridge package using twing.

Downloads

22

Readme

Static Pages / Twig

Renders documents via twig templates. This package is part of the Static Pages project.

Uses Twing and Marked packages under the hood.

Usage

import twig from '@static-pages/twig';

const renderer = twig({
	viewsDir: 'myViews',
});

const pageData = {
	title: 'Page header',
	url: 'some/page',
	content: 'My Content',
	view: 'content'
};

renderer(pageData); // returns the rendered page in a promise

Options

| Option | Type | Default value | Description | |--------|------|---------------|-------------| | view | string \| (d: Data) => string | (data.view ?? 'main') + '.twig' | Template to render. If it's a function it gets evaluated on each render call. | | views | Record<string, string> | undefined | Templates stored in memory, accessed without a filesystem implementation. | | viewsDir | string \| string[] | undefined | One or more directory path where the templates are found. | | fs | NodeJS FS API | node:fs module | Using the viewDir impiles you are using a filesystem. Here you can provide a custom implementation for that. | | filters | TwigFilters | {} | Filters in an object that gets loaded to the twig environment. | | functions | TwigFunctions | {} | Functions in an object that gets loaded to the twig environment. | | configure | (env: TwingEnvironment) => void | () => undefined | Allows advanced configuration with access to the env twig environment. | | markedEnabled | boolean | true | Register a markdown filter; uses marked. | | markedOptions | MarkedOptions | see markedOptions section | Custom options for the marked markdown renderer. |

Custom types used in the table above:

type TwigFunctions = Record<string, TwingCallable<unknown>>;
type TwigFilters = Record<string, TwingCallable<unknown>>;

Example for TwigFunctions and TwigFilters:

import { twig, raw } from '@static-pages/twig';

const renderer = twig({
	functions: {
		asset(_context, asset: string) {
			return new URL(asset, '/site/assets/').toString();
		},
	},
	filters: {
		json(_context, data) {
			return raw(JSON.stringify(data, null, '\t'));
		},
	}
});

Functions and filters can be async or sync. No restrictions like the underlying Twing package makes where you allowed to use async functions only.

Everything provided by Twing and Marked is also exported from this package for advanced use cases, see twing and marked exports.

markedOptions defaults

This package uses the default options of the official marked defaults:

In twig template files, the custom markdown filter allows you to pass markdown options to the underlying markdown renderer. Example:

{{ '~~strike~~'|markdown({ gfm: false }) }}
<p>~~strike~~</p>

~~strike~~ converted to <del>strike</del> when gfm is true (default)

Additionally there is an inline option added to the available options. This removes the paragraph tags. Example:

{{ '[foo](bar)'|markdown({ inline: true }) }}
<a href="bar">foo</a>