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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@episclera/configkit

v1.5.1

Published

🔧 Shareable configs with good defaults.

Downloads

37

Readme

GitHub Multipack

Usage

Install: npm i -D @episclera/configkit

With Prettier

In your .prettierrc.js file just put this content.

const { prettierConfig } = require('@episclera/configkit')
// OR install and import just what you need separately: const prettierConfig = require('@episclera/prettier-config')

module.exports = prettierConfig

With Commitlint

In your commitlint.config.js file just put this content.

const { commitlintConfig } = require('@episclera/configkit')
// OR install and import just what you need separately: const commitlintConfig = require('@episclera/commitlint-config')

module.exports = commitlintConfig

With Renovate

In your renovate.json file just put this content. (Do not forgot to connect/install renovate app on GitHub)

{
  "extends": ["@episclera"]
}

With Jest

In your jest.config.js file just put this content.

const { jestConfig } = require('@episclera/configkit')
// OR install and import just what you need separately: const jestConfig = require('@episclera/jest-config')

module.exports = jestConfig

With Eslint

In your .eslintrc.js file just put this content.

const { eslintConfig } = require('@episclera/configkit')
// OR install and import just what you need separately: const eslintConfig = require('@episclera/eslint-config')

module.exports = eslintConfig

With Stylelint

In your .stylelintrc.js file just put this content.

const { stylelintConfig } = require('@episclera/configkit')
// OR install and import just what you need separately: const stylelintConfig = require('@episclera/stylelint-config')

module.exports = stylelintConfig

With Babel

In your .babelrc.js file just put this content.

const { commonBabelConfig } = require('@episclera/configkit')
// OR install and import just what you need separately: const { commonBabelConfig } = require('@episclera/babel-config')

module.exports = commonBabelConfig

// OR you can mix multiple configs with "mergeConfigs" util
const {
  commonBabelConfig,
  nextBabelConfig,
  mergeConfigs,
} = require('@episclera/configkit')
// OR install and import just what you need separately: const { commonBabelConfig, nextBabelConfig } = require('@episclera/babel-config')
// const { mergeConfigs } = require('@episclera/configkit-utils')

module.exports = mergeConfigs(commonBabelConfig, nextBabelConfig)

With Webpack

In your webpack.config.js file just put this content.

const { commonWebpackConfig } = require('@episclera/configkit')
// OR install and import just what you need separately: const { commonWebpackConfig } = require('@episclera/webpack-config')

module.exports = commonWebpackConfig

// OR you can mix multiple configs with "mergeConfigs" util
const {
  commonWebpackConfig,
  packageWebpackConfig,
  mergeConfigs,
} = require('@episclera/configkit')
// OR install and import just what you need separately: const { commonWebpackConfig, packageWebpackConfig } = require('@episclera/webpack-config')
// const { mergeConfigs } = require('@episclera/configkit-utils')

module.exports = mergeConfigs(commonWebpackConfig, packageWebpackConfig)

With Postcss

In your postcss.config.js file just put this content.

const { postcssConfig } = require('@episclera/configkit')
// OR install and import just what you need separately: const postcssConfig = require('@episclera/postcss-config')

module.exports = postcssConfig

With Tailwindcss

In your tailwind.config.js file just put this content.

const { tailwindConfig } = require('@episclera/configkit')
// OR install and import just what you need separately: const tailwindConfig = require('@episclera/tailwind-config')

module.exports = tailwindConfig

With Next

Usage is similar to next-compose-plugins

In your next.config.js file just put this content.

const { nextConfig } = require('@episclera/configkit')
// OR install and import just what you need separately: const nextConfig = require('@episclera/next-config')

module.exports = nextConfig()

OR if you want to provide custom plugins or next options or webpack options

const { nextConfig } = require('@episclera/configkit')
const { mergeConfigs } = require('@episclera/configkit-utils')

module.exports = nextConfig([myPlugin], {
  publicRuntimeConfig: {
    HOME_ROUTE_PATH: '/welcome',
  },
  webpack: config =>
    mergeConfigs(config, {
      resolve: {
        alias: {
          myAlias: './myPath',
        },
      },
    }),
})

With NextI18Next

In your next-i18next.config.js file just put this content.

const { nextI18NextConfig } = require('@episclera/configkit')
// OR install and import just what you need separately: const nextI18NextConfig = require('@episclera/next-i18next-config')

module.exports = nextI18NextConfig

Contributing

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D

Or you can sponsor via Open Collective

Open Collective

Author

@episclera/configkit © Episclera, Released under the MIT License. Authored and maintained by Episclera with help from contributors (list).

If you like this repository star⭐ and watch👀 on GitHub