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

point-out

v0.1.0-alpha.2

Published

Runs a given command and scans the output for warnings/errors to create a GitLab CI Code Quality report.

Downloads

3

Readme

👉 point-out

Runs a given command and scans the output for warnings/errors to create a GitLab CI Code Quality report.

While running the command, the output is forwarded to stdout/stderr so you can still see what's happening. At the same time, the output is parsed for warnings and errors, which are then used to create a Code Quality report in the GitLab CI pipeline.

Currently parsers for the following tools are implemented:

  • CMake (warning and fatal error messages)
  • GCC, and tools that can use the same message format, like:
    • clang-format
    • clang-tidy
  • cpplint (using emacs format, which is its default)

Usage

You can run point-out -h to see the latest usage/help information (which is probably more up-to-date than this README file).

point-out [options] -- [command to parse output from]

You can use the following options:

  • -h, --help: display the help
  • -V, --version: output the version number
  • -l, --list: list all available parsers (currently not very useful, as all of them are always active)
  • -n, --no-append: if set then report will be overwritten, instead of appending to it
  • -j, --json-indent <num>: indent level for JSON output (default: "2")
  • -r, --repo-path <path>: path to the repository (default: CI_PROJECT_DIR or current working directory)
  • -a, --no-relative: do not make absolute paths relative to the repository path

Current state

The tool is still a work in progress, but should already be somewhat useable. If you run into any issues, please let me know.