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

@bloggrify/core

v3.1.2

Published

A Nuxt.js app to create a blog with Nuxt Content and Tailwind CSS

Readme

Getting started | Homepage

Bloggrify is a Nuxt Content starter specialized for blogging.

Built on the excellent Nuxt Content framework, Bloggrify provides:

Pre-configured integrations (not just dependencies)

  • 6 analytics providers (Google Analytics, Plausible, Pirsch, Umami, Fathom, Hakanai)
  • 2 newsletter services (MailerLite, Hakanai)
  • Comment systems (Hyvor Talk)
  • Social sharing

SEO & Performance out-of-the-box

  • Nuxt SEO modules pre-configured (sitemap, robots, schema.org)
  • Auto-generated RSS feed
  • Optimized for 90+ Lighthouse scores

Content components ready to use

  • YouTube/Instagram/Vimeo embeds
  • Mermaid diagrams, KaTeX math
  • Multi-author support
  • Tag & category filtering

Professional themes (not blank pages)

  • Responsive, accessible designs
  • Dark mode support
  • Customizable via single config file

Why not just use Nuxt Content directly?

You absolutely can! Bloggrify is for developers who:

  • Want a blog specifically (Nuxt Content does blogs, docs, changelogs, etc.)
  • Don't want to spend 1-2 days selecting modules and integrating analytics, comments, newsletters
  • Prefer a professional theme out-of-the-box
  • Want a single config file vs scattered configuration

If you enjoy configuring everything yourself, vanilla Nuxt Content might be better for you.

Discover all features on the official website

"Buy Me A Coffee"

If you use this project and it saves you time. How about supporting it?

Contributing

I created this blog starters because I know how tedious it is to assemble all the bricks needed to have an SEO-efficient blog, with a clean, accessible design, responsive, with features already integrated (comment system, rss feed, newsletter, sitemap etc...).

If you consider that you've really saved time, you might consider supporting this work. It's optional, but it will be much appreciated.

The first option is to offer me a virtual coffee representing the value of the time you've saved.

But you can also contribute in many other ways:

  • by talking about this project on social networks, on your blog, with your colleagues.
  • by giving this project a star on github
  • by contributing to the open source project to improve it (see below)

10% of the benefits will be donated to the Unicef foundation, an organization that helps children in need all over the world.

Contributing to the project

Make sure to install the dependencies:

# npm
npm install

# pnpm
pnpm install

Development Server

Start the development server on http://localhost:3000

Running bloggrify alone without templates won't be really useful.

# npm
npm run dev

# pnpm
pnpm run dev

Editor Support

Visual Studio Code (VS Code)

This project includes VS Code configuration files to enhance the development experience:

  • Recommended extensions for Nuxt, TailwindCSS, and TypeScript development.
  • Debug and launch configurations for client and server to improve the debugging experience.

For more information on debugging in VS Code, visit the VS Code debugging documentation.

The launch configuration is based on the example provided in the Nuxt debugging guide.

These extensions are optional and maintained by their respective developers or the VSCode users community. Contributions to the selection and recommendation of these extensions are welcome!

JetBrains IDEs

You can also debug the project in JetBrains IDEs using the Nuxt provided example JetBrains IDEs debug configuration.

Production

Build the application for production:

# npm
npm run generate

# pnpm
pnpm run generate

Locally preview production build:

# npm
npm run preview

# pnpm
pnpm run preview

Release

Each commit should respect the conventional commit format.

The basic release process is as follows:

  • Update the version in package.json
  • create a tag with the version number
  • push the tag to the repository
  • publish the release on github
  • publish the release on npm

In order to automate this process, you can use the following command:

# First, you need to install the changelogen package
npm install -g changelogen

# Then, you can run the following command to automate all the previous steps
npx changelogen --release --push && npm publish

In order to publish the release on npm, you need to be authenticated with the npm registry. You can do this by running npm login.
In order to publish the release on github, you need to be authenticated with the github registry. You can do this by creating a personal access token and setting it in your environment variables (GITHUB_TOKEN).