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

@hybrbase-staxomni/jest-config

v1.0.0

Published

A shareable jest configuration for projects.

Downloads

2

Readme

Shareable Secretlint Config

📄 About

Shareable configuration for Secretlint — a tool for linting and fixing secrets in your codebase.

The configuration provides a set of rules and settings that can be easily shared and reused across different projects, reducing the amount of boilerplate code needed to set up Secretlint in each project.

→ Purpose

Simplify the process of setting up Secretlint in a project by providing a pre-configured set of rules and settings. This package can be useful for developers who want to:

  • Use Secretlint in their project but don't want to spend time configuring it from scratch
  • Share Secretlint configuration across multiple projects
  • Avoid maintaining and updating Secretlint configuration in every project manually

The configuration includes a set of preconfigured rules, such as @secretlint/secretlint-rule-preset-recommend, that check for common mistakes and prevent secrets from being accidentally committed to the repository.

💿 Installation

To use Secretlint with @hybrbase-staxomni/secretlint-config in a mono-repository, you can install them at the root level and configure it to lint only the packages that require it. Follow these steps:

  1. Install secretlint and @hybrbase-staxomni/secretlint-config as development dependencies at the root of your mono-repository using the package manager of your choice (npm, yarn, pnpm, etc.). For example, using pnpm:

    pnpm add -Dw secretlint @hybrbase-staxomni/secretlint-config
  2. Create a .secretlintrc.json configuration file in the root of your mono-repository with the following content:

    {
      "rules": {},
      "rulesConfig": {},
      "plugins": [],
      "processor": "",
      "noDefaultConfig": true,
      "configs": {
        "@hybrbase-staxomni/secretlint-config": true
      },
      "ignore": [],
      "include": ["packages/*/**", "apps/*/**"]
    }

    In this example, Secretlint is configured to use the @hybrbase-staxomni/secretlint-config package as its configuration, and to lint only the directories in the packages and apps folders of the mono-repository.

    You can adjust the include and exclude patterns to match your specific mono-repository structure and exclude files or directories that don't need to be linted.

  3. Add a linting script to the scripts section of the package.json file at the root of your mono-repository:

    pnpm pkg set scripts.lint:secrets="secretlint"

    This will add the lint:secrets script to the scripts section of your package.json.

That's it! You can now run the lint:secrets script to lint the relevant packages in your mono-repository.