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

morbo-cli

v0.5.3

Published

… All tech debt is vermin in the eyes of Morbo!

Downloads

42

Readme

Morbo

"[to Tech Debt] Stop it, stop it. It's fine. I will destroy you"

Getting started

yarn add morbo

Recommended: Create a .morborc file

// Default options
{
  "scanPath": process.cwd(),
  "ignoredDirectories": [
    "**/node_modules/**",
    ".git/**",
    ".hg/**",
    "**/flow-typed/**",
    "**/morbo_report/**",
    "build/**",
    "dist/**",
    "config/**",
  ],
  "filesToScan": ["**/*.{js,php,go}"],
  "fileEncoding": "utf8",
  "lineLengthLimit": 1000,
  "skipChecks": [],
  "customDefinitions": {},
  "openReportOnCompletion": false,
  "projectId": "YOUR_MORBO_PROJECT_ID",
  "sendReportOnCompletion": false,
  "showGitBlame": true,
  "showSkippedChecks": false,
}

Configure Options (In More Detail)

  • scanPath: The path to scan through for notes, defaults to process.cwd()
  • ignoredDirectories: Glob patterns for directories to ignore. Passes these straight to minimatch so check there for more information on proper syntax.
  • filesToScan: Glob patterns for files to scan. Also uses minimatch.
  • fileEncoding: The encoding the files scanned will be opened as.
  • lineLengthLimit: The number of max characters a line can be before Morbo gives up and doen not scan it for matches. If a line is too long, the regular expression will take an extremely long time to finish. You have been warned!
  • skipChecks: List of check names to skip. Valid options: note, optimize, todo, hack, xxx, fixme, bug, line. line will disable the line length warning.
  • customDefinitions: Hashmap of custom defined regex terms. Follows the following format:
"customDefinitions": {
  "myCustomDefinition": {
    "description": "Replace all occurences of @stylus with emotion components",
    "regex": "@stylus",
    "label": "Stylus Components"
  }
}

CLI Usage

morbo --help

More Examples

Take a look at the examples/annotation.test.js file, all of those comments in there are supported and expected to parse with Morbo.


Thanks to JohnPostlethwait and his project fixme on which this project gets its roots