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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@riktajs/ssr

v0.11.6

Published

Server-Side Rendering (SSR) support for Rikta framework with React, Vue, and other frontend frameworks

Readme

@riktajs/ssr

Server-Side Rendering (SSR) support for Rikta framework. Enable your Rikta application to render React, Vue, and other frontend frameworks on the server, making it a fullstack framework.

Features

  • 🚀 Vite-powered - Leverages Vite for blazing fast HMR and builds
  • ⚛️ React & Vue support - First-class support for React and Vue frameworks
  • 🔥 Hot Module Replacement - Full HMR support in development mode
  • 📦 Zero Config - Works out of the box with sensible defaults
  • 🛠️ Fastify Integration - Seamlessly integrates with Fastify server
  • 💎 TypeScript Ready - Full TypeScript support with proper types

Installation

# Using npm
npm install @riktajs/ssr vite

# Using pnpm
pnpm add @riktajs/ssr vite

# For React
npm install react react-dom
npm install -D @vitejs/plugin-react

# For Vue
npm install vue
npm install -D @vitejs/plugin-vue

Quick Start

1. Create your Vite config

// vite.config.ts
import { defineConfig } from 'vite';
import react from '@vitejs/plugin-react';

export default defineConfig({
  plugins: [react()],
  build: {
    rollupOptions: {
      input: {
        client: './src/entry-client.tsx',
      },
    },
  },
  ssr: {
    noExternal: ['@riktajs/core'],
  },
});

2. Create entry files

Server Entry (src/entry-server.tsx):

import React from 'react';
import { renderToString } from 'react-dom/server';
import { App } from './App';

export function render(url: string, context: Record<string, any> = {}) {
  const html = renderToString(<App url={url} context={context} />);
  return html;
}

Client Entry (src/entry-client.tsx):

import React from 'react';
import { hydrateRoot } from 'react-dom/client';
import { App } from './App';

hydrateRoot(document.getElementById('app')!, <App />);

3. Register the SSR plugin

import { Rikta } from '@riktajs/core';
import { ssrPlugin } from '@riktajs/ssr';
import { fileURLToPath } from 'url';
import { dirname, resolve } from 'path';

const __dirname = dirname(fileURLToPath(import.meta.url));

async function bootstrap() {
  const app = await Rikta.create({ port: 3000 });

  // Register SSR plugin
  await app.server.register(ssrPlugin, {
    root: resolve(__dirname, '..'),
    entryServer: './src/entry-server.tsx',
    template: './index.html',
  });

  // Serve all routes with SSR
  app.server.get('*', async (request, reply) => {
    const html = await app.server.ssr.render(request.url, {
      user: request.user,
    });
    return reply.type('text/html').send(html);
  });

  await app.listen();
  console.log('🚀 Server running at http://localhost:3000');
}

bootstrap();

Configuration

SSR Options

| Option | Type | Default | Description | |--------|------|---------|-------------| | root | string | process.cwd() | Project root directory | | entryServer | string | './src/entry-server' | Path to server entry file | | template | string | './index.html' | Path to HTML template | | dev | boolean | auto | Enable development mode (auto-detected from NODE_ENV) | | buildDir | string | 'dist' | Build output directory | | ssrManifest | string | 'ssr-manifest.json' | SSR manifest filename |

HTML Template

Your index.html should include placeholders for SSR content:

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8" />
  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
  <title>My Rikta App</title>
  <!--head-tags-->
</head>
<body>
  <div id="app"><!--ssr-outlet--></div>
  <script type="module" src="/src/entry-client.tsx"></script>
</body>
</html>

API Reference

Decorators

@SsrController(options?)

Marks a class as an SSR controller with optional route prefix and default options.

import { SsrController, Ssr, Get, Head } from '@riktajs/ssr';

@SsrController({
  prefix: '/pages',
  defaults: {
    og: { siteName: 'My Site', type: 'website' },
    twitter: { site: '@mysite' },
    head: [Head.meta('author', 'Your Name')],
  },
})
export class PageController {
  @Get('/')
  @Ssr({ title: 'Home Page', description: 'Welcome to our site' })
  home() {
    return { page: 'home', features: ['fast', 'secure'] };
  }
}

The defaults option allows setting common metadata for all routes in the controller. Individual @Ssr() decorators can override or extend these defaults:

  • Simple properties: route overrides defaults
  • Nested objects (og, twitter, cache): merged (route takes precedence)
  • Arrays (head): concatenated

@Ssr(options)

Configures SSR metadata for a route handler.

@Ssr({
  title: 'Page Title',
  description: 'SEO description',
  og: { image: '/og-image.png', type: 'website' },
  twitter: { card: 'summary_large_image' },
  canonical: 'https://example.com/page',
  robots: 'index, follow',
  cache: { maxAge: 60, staleWhileRevalidate: 120 },
})

Client-Side Navigation Data Fetching

When using @riktajs/react with SSR, the framework supports automatic data fetching for client-side navigation. When a client navigates to a new page, the RiktaProvider fetches the SSR data via a special header:

X-Rikta-Data: 1

The server responds with JSON instead of full HTML:

{
  "data": { "page": "about", "features": [...] },
  "url": "/about",
  "title": "About - My App",
  "description": "Learn more about our company"
}

This enables:

  • Seamless navigation without page reloads
  • Consistent data between SSR and client navigation
  • SEO metadata passed to client for title updates

ssrPlugin

Fastify plugin that enables SSR capabilities.

import { ssrPlugin, SsrOptions } from '@riktajs/ssr';

await app.server.register(ssrPlugin, options);

SSR Plugin Options

| Option | Type | Description | |--------|------|-------------| | root | string | Project root directory | | entryServer | string | Path to server entry file | | template | string | Path to HTML template | | dev | boolean | Enable development mode | | buildDir | string | Build output directory | | container | Container | DI container for guards, middleware, interceptors support |

Guards, Middleware, and Interceptors

SSR routes fully support Rikta's decorator-based guards, middleware, and interceptors. To enable this functionality, pass the container option when registering the plugin:

const app = await Rikta.create({
  port: 3000,
  controllers: [ApiController],
});

await app.server.register(ssrPlugin, {
  root: resolve(__dirname, '..'),
  entryServer: './src/entry-server.tsx',
  template: './index.html',
  // Enable guards, middleware, interceptors on SSR routes
  container: app.container,
});

app.server.registerSsrController(PageController);

Using Guards on SSR Routes

import { Get, UseGuards, Req } from '@riktajs/core';
import type { FastifyRequest } from 'fastify';
import { SsrController, Ssr } from '@riktajs/ssr';
import { AuthGuard } from './guards/auth.guard.js';

@SsrController()
export class PageController {
  // Public page - no guard
  @Get('/')
  @Ssr({ title: 'Home' })
  home() {
    return { page: 'home' };
  }

  // Protected page - requires authentication
  @Get('/dashboard')
  @UseGuards(AuthGuard)
  @Ssr({ title: 'Dashboard', robots: 'noindex' })
  dashboard(@Req() request: FastifyRequest) {
    const user = (request as any).user;
    return {
      page: 'dashboard',
      user: { id: user.id, name: user.name },
    };
  }
}

Example Guard Implementation

import type { Guard, ExecutionContext } from '@riktajs/core';

export class AuthGuard implements Guard {
  canActivate(context: ExecutionContext): boolean | Promise<boolean> {
    const request = context.switchToHttp().getRequest();
    
    const authToken = request.headers['x-auth-token'];
    
    if (authToken) {
      // Validate token and attach user to request
      request.user = { id: 'user-123', name: 'John Doe' };
      return true;
    }
    
    return false; // Returns 403 Forbidden
  }
}

Using Middleware on SSR Routes

import { Get, UseMiddleware } from '@riktajs/core';
import { SsrController, Ssr } from '@riktajs/ssr';
import { LoggingMiddleware } from './middleware/logging.middleware.js';

@SsrController()
export class PageController {
  @Get('/tracked')
  @UseMiddleware(LoggingMiddleware)
  @Ssr({ title: 'Tracked Page' })
  trackedPage() {
    return { page: 'tracked' };
  }
}

Using Interceptors on SSR Routes

import { Get, UseInterceptors } from '@riktajs/core';
import { SsrController, Ssr } from '@riktajs/ssr';
import { CacheInterceptor } from './interceptors/cache.interceptor.js';

@SsrController()
export class PageController {
  @Get('/cached')
  @UseInterceptors(CacheInterceptor)
  @Ssr({ title: 'Cached Page' })
  cachedPage() {
    return { page: 'cached', timestamp: Date.now() };
  }
}

SsrService

Injectable service for programmatic SSR control.

import { Injectable, Autowired } from '@riktajs/core';
import { SsrService } from '@riktajs/ssr';

@Injectable()
class MyController {
  @Autowired()
  private ssr!: SsrService;

  async render(url: string) {
    return this.ssr.render(url, { data: 'context' });
  }
}

Methods

render(url: string, context?: Record<string, any>): Promise<string>

Renders the application for the given URL and returns the full HTML.

transformIndexHtml(url: string, html: string): Promise<string>

Transforms the HTML template with Vite's transformations (in dev mode).

Production Build

1. Build for production

# Build client
vite build --outDir dist/client

# Build server
vite build --outDir dist/server --ssr src/entry-server.tsx

2. Start production server

const app = await Rikta.create({ port: 3000 });

await app.server.register(ssrPlugin, {
  root: resolve(__dirname, '..'),
  entryServer: './dist/server/entry-server.js',
  template: './dist/client/index.html',
  dev: false,
  buildDir: 'dist/client',
});

Vue Support

For Vue applications, the setup is similar:

// vite.config.ts
import { defineConfig } from 'vite';
import vue from '@vitejs/plugin-vue';

export default defineConfig({
  plugins: [vue()],
});
// src/entry-server.ts
import { createApp } from './main';
import { renderToString } from 'vue/server-renderer';

export async function render(url: string, context: Record<string, any> = {}) {
  const { app } = createApp();
  const html = await renderToString(app);
  return html;
}

License

MIT