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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@iampersoncool/simple-ssr

v1.0.3

Published

# Notes

Readme

Simple SSR library

Notes

  • The vite plugin will read the viewsDir from the view engine and recursively add all the files in the directories to the vite config's build.rollupOptions.input.
  • For all view engines, you MUST set the file extension to .html, because vite throws an error if it does not recognize the file extension as html, javascript, or typescript. This also means you must also write your templates in html files, which should be fine.
  • If you are using ejs or eta, you cannot use the default delimiters (<% and %>) because vite thinks these are html tags, which it does not recognize, throwing an error. The EtaViewEngine supports changing delimiters, as shown in the example usages. You can change it to anything you want, I recommend something like {% and %}.
  • The viewsDir when you create a instance of ViewEngine has to be relative to your vite config's root. For example, if your root was at ./client and your views was in that folder, you would put 'views'.

Example directory structure

root
  ├── server.ts
  ├── config.ts
  └── vite.config.ts

Example server

server.ts

import FastifySimpleSSR from '@iampersoncool/fastify-simple-ssr/FastifySimpleSSR';
import { engine } from './config.js';

import fastify from 'fastify';

const ssr = new FastifySimpleSSR();

const app = fastify();

const middleware =
  process.env.NODE_ENV === 'production'
    ? ssr.getProdMiddleware()
    : ssr.getDevMiddleware();

app.register(middleware, {
  viewEngine: engine,
});

Example usage(EdgeViewEngine)

config.ts

import EdgeViewEngine from '@iampersoncool/simple-ssr-edge';

export const engine = new EdgeViewEngine(
  'views',
  ['{{', '}}'],
  '.html',
  process.env.NODE_ENV === 'production'
);

Example usage(EtaViewEngine)

config.ts

import EtaViewEngine from '@iampersoncool/simple-ssr-eta';

export const engine = new EtaViewEngine(
  'views',
  ['{%', '%}'],
  '.html',
  process.env.NODE_ENV === 'production'
);

Vite config

vite.config.ts

import SimpleSSRVitePlugin from '@iampersoncool/simple-ssr/vite-plugin';
import { defineConfig } from 'vite';
import { engine } from './config';

export default defineConfig({
  root: 'client',
  build: {
    outDir: 'dist',
  },
  plugins: [SimpleSSRVitePlugin({ viewEngine: engine })],
});