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

@meistrari/mise-en-place

v2.13.0

Published

Meistrari `mise-en-place` ---

Readme

Meistrari mise-en-place

Before cooking anything, it's important to have your mise en place ready. This project helps you set up your development environment with essential configurations and tools.

Installation

Add mise-en-place postinstall to your project's package.json postinstall script to automatically set up the mise en place after installing dependencies:

{
    "scripts": {
        "postinstall": "mise-en-place postinstall"
    }
}

Then install the package as a development dependency and run the postinstall script:

bun i -D @meistrari/mise-en-place
bunx mise-en-place postinstall

It will also setup the initial mise-en-place in your project. Which includes:

  • Adding a Makefile with useful commands.
  • Adding an .editorconfig file.
  • Adding ESLint configuration.
  • Adding TypeScript configuration.
  • Setting up postinstall script to keep all @meistrari/* packages up to date.

Features

Keep all @meistrari/* packages up to date

By adding the postinstall script to run mise-en-place postinstall, every time you run install your dependencies, it will check for the latest versions of all @meistrari/* packages in your project and update them if necessary.

This process will add a leading caret (^) to the version range if it is not already present. Which means that it will update to the latest minor and patch versions automatically but never the major version.

Makefile

Commands with ## after the target are 'public' commands and are intended to be used by developers and will show up in the help message.

The other commands are 'hidden' and are intended to be used by automations or by other 'public' commands.

If you installed @meistrari/mise-en-place on a parent directory, you may need to set the MISE_EN_PLACE_INSTALL_DIR variable before including the Makefile:

MISE_EN_PLACE_INSTALL_DIR=.. # Parent directory
-include $(MISE_EN_PLACE_INSTALL_DIR)/node_modules/@meistrari/mise-en-place/Makefile

EditorConfig

Since the editorconfig file don't support extending from other files, the postinstall script will always copy the .editorconfig file from this project to your project root.

Eslint Config

Add the following code in your eslint.config.mjs to include this project's ESLint configuration:

export { default } from '@meistrari/mise-en-place/eslint'

If some rules needs to be updated, you can update the rules in this project (preferrable) or customize them in your own configuration (not preferrable). You probably don't need to customize the configuration, since it is already designed to be a good starting point for most projects. Remember that customizing too much can make your project diverge from the standard and make it harder to maintain.

If you understand the risk and NEED to customize the configuration, you can import the default configuration and extend it:

import miseEnPlaceEslintConfig from '@meistrari/mise-en-place/eslint'

export default miseEnPlaceEslintConfig
    .append({
        rules: {
            // your custom rules here
        }
    })

TSConfig

Add the following code in your tsconfig.json to include this project's TypeScript configuration:

{
    "extends": "./node_modules/@meistrari/mise-en-place/tsconfig.base.json"
}