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

@cycjimmy/config-lib

v4.0.0

Published

Personal collection of configs

Readme

config-lib

libraries sourcerank Release date semantic-release npm license

Personal collection of configs.

Every entry is a standalone ES module, so you import exactly the one you need and nothing else is evaluated. TypeScript declarations ship next to the JavaScript.

Requirements

Node.js ^22.18.0 || >=24.11.0.

Install

NPM version npm download

# via npm
$ npm install @cycjimmy/config-lib --save

# or via yarn
$ yarn add @cycjimmy/config-lib

Usage

import production from '@cycjimmy/config-lib/dist/terser/4.x/production.js'

// do something
// ...

CommonJS consumers can still require the ES modules on Node.js >= 22.12, where a require of an ES module is supported:

const { default: production } = require('@cycjimmy/config-lib/dist/terser/4.x/production.js')

The declarations are resolved from the same path:

import type { TerserProductionOptions } from '@cycjimmy/config-lib/dist/terser/4.x/production.js'
import terserProduction from '@cycjimmy/config-lib/dist/terser/4.x/production.js'

const custom: TerserProductionOptions = {
  ...terserProduction,
  ecma: 2015,
}

Migration from v3 to v4

v4 is a breaking release: the package is ESM only, the build moved to Vite and the sources are written in TypeScript.

| v3 | v4 | | --- | --- | | @cycjimmy/config-lib/esm/<entry>.js | @cycjimmy/config-lib/dist/<entry>.js | | @cycjimmy/config-lib/cjs/<entry>.cjs | removed - use the ES module (or require() on Node.js >= 22.12) | | Node.js 18 | Node.js ^22.18.0 \|\| >=24.11.0 | | no type declarations | one .d.ts next to every entry |

The import statements keep the explicit .js extension, the export shape of every entry is unchanged.

Entries

chore

| Entry | Description | | --- | --- | | dist/chore/myBanner.js | Renders the licence banner comment for a bundle. | | dist/chore/judgeProcessEnv.js | IS_DEVELOPMENT / IS_PRODUCTION / IS_DEPLOYMENT flags, read once from process.env.NODE_ENV when the module is evaluated. |

terser

| Entry | Description | | --- | --- | | dist/terser/4.x/production.js | Production minify options for terser 4.x. |

terserWebpackPlugin

| Entry | Description | | --- | --- | | dist/terserWebpackPlugin/2.x/production.js | TerserPlugin options sharing the terser 4.x production options. | | dist/terserWebpackPlugin/2.x/working.js | Same options with the licence comments disabled. |

imageWebpackLoader

| Entry | Description | | --- | --- | | dist/imageWebpackLoader/6.x/production.js | Production loader options for image-webpack-loader 6.x (svgo 1.x plugin shape). | | dist/imageWebpackLoader/8.x/production.js | Production loader options for image-webpack-loader 8.x (svgo 2.x plugin shape). |

browsersync

| Entry | Description | | --- | --- | | dist/browsersync/2.x/middleware/makeAjax.js | browser-sync middleware factory that mocks an Ajax endpoint: makeAjax({ apiName, data, timeout }). |

semanticRelease

| Entry | Description | | --- | --- | | dist/semanticRelease/15.x/makeConfig.js | Builds a semantic-release plugins array from explicit flags. | | dist/semanticRelease/15.x/makeCommonConfig.js | The same builder with changelog and git enabled. | | dist/semanticRelease/19.x/makeConfigWithPgkRootForLibrary.js | Preset that builds the package and publishes it from .release. |

import makeConfigFromConfigLib from '@cycjimmy/config-lib/dist/semanticRelease/19.x/makeConfigWithPgkRootForLibrary.js'

export default makeConfigFromConfigLib({
  githubOptions: {
    assets: ['dist/index.js']
  },
})

Development

$ npm ci
$ npm run type-check   # tsc --noEmit
$ npm run lint         # eslint
$ npm test             # vitest
$ npm run package      # build dist and assemble .release

npm run package builds the declarations with tsc, transpiles every source file to dist/ with Vite (one module per file), then copies dist, README.md and LICENSE into .release, which is the directory published to npm.

License

MIT