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

pragmatic-view-express

v0.0.2

Published

PragmaticView templates in Express

Downloads

11

Readme

npm node Coverage Status Gitlab pipeline status (branch)

PragmaticView Express

PragmaticView plugin for Express.

npm install --save pragmatic-view pragmatic-view-express

Typed for Typescript

Getting started

Documentation

Adding custom templating engine to Express is quite inconvenient. That's why PragmaticView offers helper method that takes care of everything. Just pass express app to the helper method.

// ES6
import pragmaticView from 'pragmatic-view-express';
// CommonJS
const pragmaticView = require('pragmatic-view-express').default;

// creating express app
const app = express();

pragmaticView(app);

app.get('/', (req, res) => {
	res.render('home');
});

app.listen(8080);

You may want to pass config as additional argument.

Config:

  • templateExtension extension of template files (.jsx, .tsx or .pv), default .pv
  • templateDir directory of templates (automaticaly sets app.set('views', './directory')),
  • defaultLayout path to default layout template, relative is evalutaed accordint to templateDir
  • registerOptions additional template transpilation options, learn more
pragmaticView(app, {
	templateDir: path.resolve(process.cwd(), './views'),
	templateExtension: '.jsx'
});

Rendering templates

Templates are rendered through express' response.render method that accept two argument. First argument is relative path to the template without extansion (realtive to Express' template directory set either in templateDir or app.set('views', './directory')). Second argument is either context object or options object.

app.get('/aboutus', (req, res) => {
	let context = {
		title: 'My page'
	}
	res.render('home', context);
});

options object can include

  • layout realative path (works like path to template), if false is passed instead of string, no layout is used
  • context context object
// Rednering with different layout
app.get('/aboutus', (req, res) => {
	let context = {
		title: 'My page'
	}
	res.render('home', {
		layout: 'bluelayout',
		context: {
			title: 'My page'
		}
	});
});

// Rednering without layout
app.get('/aboutus', (req, res) => {
	let context = {
		title: 'My page'
	}
	res.render('home', {
		layout: false,
		context: {
			title: 'My page'
		}
	});
});