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

mise-projen

v0.0.6

Published

Add [mise](https://mise.jdx.dev) support to any [projen](https://projen.io) project via a `constructs` mixin.

Readme

mise-projen

Add mise support to any projen project via a constructs mixin.

Mise generates and maintains a mise.toml file, and lets multiple components/plugins each contribute a fragment of configuration (tools, tasks, env, settings, ...) that gets deep-merged into a single file.

Installation

pnpm add -D mise-projen

constructs and projen are peer dependencies and must already be present in your project.

Usage

Apply the mixin to any projen project with project.with(...):

import { cdk } from 'projen';
import { Mise } from 'mise-projen';

const project = new cdk.JsiiProject({
  // ...
});

project.with(new Mise({
  config: {
    tools: {
      node: ['24'],
      pnpm: ['11'],
    },
  },
}));

Configure the mixin before applying it, or apply several Mise mixins to the same project - all contributions are merged:

const mise = new Mise();
mise.addTools({ node: '24', pnpm: ['11', '10'] });
mise.merge({ env: [{ FOO: 'bar' }] });

project.with(mise);

MiseFile

Mise.applyTo() is backed by MiseFile, the component that actually owns the generated mise.toml. Use it directly for a non-mixin API, or to reach into a project that already has mise configured:

import { MiseFile } from 'mise-projen';

const miseFile = MiseFile.ensure(project);
miseFile.addTools({ python: '3.12' });
miseFile.merge({ tasks: { build: { run: 'pnpm build' } } });

MiseFile.of(project) returns the existing instance (or undefined if none exists yet); MiseFile.ensure(project, options) gets or creates it.

Configuration typing

Configuration fragments are typed against MiseTomlSchema, generated from mise's own JSON schema, so config/merge() give you autocomplete and type checking for the full mise.toml shape.

API Reference

See API.md for the full generated API reference.