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

@juicyllama/repo

v0.9.0

Published

A collection of utilities for working with repositories.

Readme

Visit the JuicyLlama to learn more.

@juicyllama/repo

A package for repo configuration helpers

Install

npm install @juicyllama/repo

Turbo

We use TurboRepo for handling full projects within a single monorepo.

On installation of @juicyllama/repo it will sync your shared turbo file and generate the turbo.json, this is due to limitations with TurboRepos extends functionality.

If you need to make changes or extend this, simply update turbo.shared.json and run node ./node_modules/@juicyllama/repo/dist/turbo/sync-turbo.mjs

Root file

//turbo.shared.json
{
  "extends": ["@juicyllama/repo/turbo"],
  "globalEnv": [
    ...
  ]
}

Linting

Were using biomejs for linting and formatting.

//biome.json
{
  "extends": ["@juicyllama/repo/biome"]
}

Read More

TypeScript

You can extend the pre-build typescript configurations here:

NestJs

//tsconfig.json
{
	"extends": "@juicyllama/repo/typescript/nestjs.json"
}

Next.Js

//tsconfig.json
{
	"extends": "@juicyllama/repo/typescript/nextjs.json"
}

Nuxt

//tsconfig.json
{
	"extends": "@juicyllama/repo/typescript/nuxt.json"
}

React

//tsconfig.json
{
	"extends": "@juicyllama/repo/typescript/react-library.json"
}

Base

//tsconfig.json
{
	"extends": "@juicyllama/repo/typescript/base.json"
}

Jest

Shared Jest configs are available:

//jest.config.ts
import { Config } from '@juicyllama/repo/jest/base'

export default Config

NestJS config:

//jest.config.ts
import { nestConfig } from '@juicyllama/repo/jest/nest'

export default nestConfig

Next.js config:

//jest.config.ts
import { nextConfig } from '@juicyllama/repo/jest/next'

export default nextConfig

Husky

The package will copy over .husky folder if it does not already exist with a recommended default setup.

IDE

VS Code

A suggested vs code settings file which complements this set up can be found in ./.vs-code/settings.json