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

nuxt-run

v1.2.0

Published

Bundle server run scripts into standalone mjs entries during the Nuxt/Nitro build

Readme

nuxt-run

npm version npm downloads License Nuxt

Sponsored by


Runnable scripts in any environment.

Useful when you need to:

  • Run service code against an environment without pulling secrets down
  • Avoid HTTP endpoints just to trigger server code
  • Skip a queue when a one-shot or cron script is enough

Getting started

npm install -D nuxt-run
// nuxt.config.ts
export default defineNuxtConfig({
  modules: ['nuxt-run'],
  run: {
    runDir: 'server/run',
    runPattern: '**/index.{ts,js,mjs}',
  },
})

Add a script under server/run/<name>/index.ts:

// server/run/seed/index.ts
const {
  database: {
    url,
  },
} = useRuntimeConfig()

const orm = new MyOrm(url)

const seed = async () => {
  await orm.insert(...)
}

seed().catch((e) => {
  console.error(e)
  process.exit(1)
})

In dev:

nuxt dev
node .nuxt/dev/run/seed/index.mjs

Post build:

nuxt build
node .output/server/run/seed/index.mjs

Scripts share Nitro's module graph, so useRuntimeConfig() and server/utils work.

More detail: Getting started.

Contribution

npm install
npm run dev:prepare   # generate type stubs
npm run dev            # develop with the playground
npm run dev:build      # production build of the playground
npm run lint
npm run test
npm run vp:dev         # VitePress docs site
npm run release