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

@secretlint/secretlint-rule-filter-comments

v9.0.0

Published

secretlint-disable comment directive.

Downloads

41,300

Readme

@secretlint/secretlint-rule-filter-comments

secretlint-disable comment directive.

Install

Install with npm:

npm install @secretlint/secretlint-rule-filter-comments

Usage

Via .secretlintrc.json(Recommended)

{
  "rules": [
    {
      "id": "@secretlint/secretlint-rule-filter-comments"
    }
  ]
}

secretlint-disable directives

  • secretlint-disable disable
  • secretlint-enable: enable again
  • secretlint-disable-line: ignore current line
  • secretlint-disable-next-line: ignore next line

Examples

To temporarily disable rule warnings in your file, use block comments in the following format:

You can replace // with any characters like # or /* etc... @secretlint/secretlint-rule-filter-comments only look up /(?<type>secretlint-(?:disable-next-line|disable-line|disable|enable))(?<options>.*)/g pattern.

// secretlint-disable

THIS IS IGNORED SECRET

// secretlint-enable

THIS WILL REPORTED SECRET

You can also disable or enable warnings for specific rules:

/* secretlint-disable @secretlint/secretlint-rule-github */
const TOKEN = "ghs-<github token>";

/* secretlint-enable @secretlint/secretlint-rule-github */

To disable rule warnings in an entire file, put a /* secretlint-disable */ block comment at the top of the file. Of course, you can use .secretlintignore instead of it.

// secretlint-disable

.... all ignored ....

You can also disable or enable specific rules for an entire file:

// secretlint-disable @secretlint/secretlint-rule-github

GITHUB TOKEN WILL NOT DETECT!

To disable all rules on a specific line using secretlint-disable-line:

THIS IS SECRET BUT IT WILL BE IGNORED // secretlint-disable-line

To disable all rules on a next line using secretlint-disable-nextline:

// secretlint-disable-next-line
THIS IS SECRET BUT IT WILL BE IGNORED

All disable/enable syntax can include comment using -- comment.

// secretlint-disable @secretlint/secretlint-rule-github -- disable github rule

MessageIDs

IGNORE_MESSAGE

disable by secretlint-disable comment

Ignored messages. It will not appear on result.

Options

  • [ ] No Options yet

Changelog

See Releases page.

Running tests

Install devDependencies and Run npm test:

npm test

Contributing

Pull requests and stars are always welcome.

For bugs and feature requests, please create an issue.

  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

Author

License

MIT © azu