fastify/point-of-view

Template rendering plugin for Fastify

Hosted by OpenJS Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

fastify/point-of-view has 350+ stars and 90+ forks on GitHub, is written in JavaScript, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:Plugin / ExtensionCategory(s):Backend FrameworksWeb Development
Added to GitGenius on October 15th, 2026
Created on March 30th, 2017
Open Issues & Pull Requests: 9 (+0)
GitHub issues: Enabled
Number of forks: 93
Total Stargazers: 382 (+0)
Total Subscribers: 17 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.9 hours
Mean response time: 9.9 days
90th percentile: 16.1 days
Tracked items: 101

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,320 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • stale (15)
  • bug (3)
  • feature request (2)
  • good first issue (2)
  • github actions (1)
  • semver-minor (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Point-of-view is a template rendering plugin for Fastify that decorates the reply interface with view methods for managing template engines.

The plugin solves the problem of rendering templated responses in Fastify applications by providing a unified interface to multiple template engines. It supports a wide range of engines including EJS, Nunjucks, Pug, Handlebars, Mustache, Twig, Liquid, doT, Eta, Edge, and Squirrelly. The approach works by decorating Fastify's reply object with `view` and `viewAsync` methods that handle template rendering. The tool automatically manages caching behavior based on environment: in production it heavily caches templates and compiled functions for performance, while in development it reloads templates on each request to support iterative development.

Developers should choose this plugin when building Fastify applications that need server-side template rendering. It suits projects requiring flexibility in template engine choice, as the same plugin interface works across multiple engines without requiring engine-specific code. The plugin is particularly relevant for applications where rendering performance matters, as benchmarks show Fastify with point-of-view achieves significantly higher request throughput than Express-based alternatives.

The project maintains active development with ongoing refinement of its API, as evidenced by the introduction of `viewAsync` as a replacement for the earlier `view` method and the removal of deprecated engine support like ejs-mate and marko to encourage users toward maintained alternatives. The codebase shows responsiveness to ecosystem changes by dropping support for unmaintained template engines while directing users to dedicated packages where appropriate.