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

@m78/build-tools

v0.0.20

Published

simple builder for M78 projects, which also contain several developer tools.

Readme

simple builder for M78 projects, which also contain several developer tools.

usage

First, add m78-build-tools to your project, use your favorite package manager

auto inject config

generate config via cli, ⚠️ this operation will be overwrite same name file and change package.json

npm init -y
npx m78-build-tools init

will create below files:

.eslintrc.cjs
.npmrc
.prettierrc.cjs
jest.config.js
m78-lib.config.js
tsconfig.json
tsconfig.lib.json

and modify these fields in package.json

scripts 
devDependencies 
files 
main 
type 
typings 
publishConfig

build

  1. Make sure m78-lib.config.js exist in project root. for config detail, see defineConfig.d.ts
import sass from "sass";
import { mkdir, writeFile } from "node:fs/promises";
import { defineConfig } from "@m78/build-tools/defineConfig.js";
// import { defineCommonConfig } from "@m78/build-tools/defineConfig.js"; // commonConfig if need
// export const commonConfig = defineCommonConfig({ ... })

export default defineConfig({
  build: [
    {
      inpDir: "src",
      outDir: "esm",
      swcConfig: {
        module: {
          type: "es6",
        },
      },
    },
  ],
});

2.run npx m78-build-tools build

pass --skip-declaration-emit to block the student declaration file

test

built-in test by jest and @testing-library/react.

  1. add jest.config.js to project root.
export { default } from "@m78/lib-build/jest.config.js";
  1. write test code

  2. run test

npx jest

example

start dev server, run your code.

suppose the root directory has the following code

examples
	| - func1
		|- index.html
		|- xxx.tsx		# use in index.html <script type="module" src="./index.tsx"></script>
  | - func2
		|- index.html

run the specified example

npx m78-build-tools example func1	# run func1

lint

provide eslint and prettier base config, usage by follow:

  1. add config

.eslintrc.cjs

module.exports = {
  extends: [require.resolve("@m78/lib-build/.eslintrc.cjs")],
  rules: {},
};

.prettierrc.cjs

const config = require("@m78/lib-build/.prettierrc.cjs");

module.exports = {
  ...config,
};