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

@dropinblog/react-tanstack-start

v1.0.0

Published

TanStack Start adapter for @dropinblog/react-core with server-side rendering support

Readme

@dropinblog/react-tanstack-start

TanStack Start adapter for @dropinblog/react-core with server-side rendering support.

Features

  • Full server-side rendering (SSR) support
  • Pre-built file-based route templates
  • SEO-optimized with TanStack Router's head() API
  • RSS feeds and XML sitemap included
  • Support for React 18 and 19
  • Easy CLI installation

Installation

npm install @dropinblog/react-tanstack-start @dropinblog/react-core

Quick Start

1. Configure Environment Variables

Create a .env file in your TanStack Start project. These are server-only, so do not prefix them with VITE_ (that would expose the API token to the browser):

DROPINBLOG_BLOG_ID=your_dropinblog_blog_id
DROPINBLOG_API_TOKEN=your_dropinblog_api_token

2. Install Templates

Use the CLI to install the blog routes:

npx dropinblog-tanstack install

This will create all necessary blog routes in your project:

  • /blog - Main blog list
  • /blog/page/{page} - Paginated blog list
  • /blog/category/{slug} - Category pages
  • /blog/category/{slug}/page/{page} - Paginated category pages
  • /blog/author/{slug} - Author pages
  • /blog/author/{slug}/page/{page} - Paginated author pages
  • /blog/{slug} - Single post pages
  • /blog/sitemap.xml - Sitemap
  • /blog/feed - RSS feed
  • /blog/feed/category/{slug} - Category RSS feeds
  • /blog/feed/author/{slug} - Author RSS feeds

To mount the blog at a different path (e.g. /news), pass --path:

npx dropinblog-tanstack install --path news

Note: also set your blog's URL in DropInBlog. The path your app responds at is controlled by where the routes live (--path), but the permalinks, canonical tags, RSS, and sitemap inside the rendered HTML come from your blog's Blog URL setting in DropInBlog. For everything to line up, set that URL to match (e.g. https://yoursite.com/news).

3. Render HeadContent and Scripts in your root route

DropInBlog's SEO tags, styles and scripts are emitted from each route's head(). For them to render, your root route (src/routes/__root.tsx) must render <HeadContent /> in the document <head> and <Scripts /> at the end of <body>:

import { HeadContent, Scripts, createRootRoute } from '@tanstack/react-router';

export const Route = createRootRoute({
  component: () => (
    <html>
      <head>
        <HeadContent />
      </head>
      <body>
        <Outlet />
        <Scripts />
      </body>
    </html>
  ),
});

The installer checks for these and warns if they're missing.

License

MIT