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

stylelint-teamcity-reporter

v1.1.1

Published

Outputs [stylelint](https://stylelint.io) results compatible with [TeamCity](https://confluence.jetbrains.com/display/TCD10/Build+Script+Interaction+with+TeamCity#BuildScriptInteractionwithTeamCity-ReportingTests).

Downloads

1,035

Readme

stylelint-teamcity-reporter

Outputs stylelint results compatible with TeamCity.

Usage

Install from npm:

npm install --save-dev stylelint-teamcity-reporter

or Yarn:

yarn add -D stylelint-teamcity-reporter

Then, set stylelint's custom formatter to the package. To do this from CLI, use:

stylelint \"**/*.css\" --custom-formatter=node_modules/stylelint-teamcity-reporter

Configuration

Without any configuration, stylelint results will be reported as tests on a TeamCity build ("reporter": "errors"). You can also configure it to produce code inspection-style output ("reporter": "inspections"), which is displayed on the "Code Inspections" tab in TeamCity. Settings are looked for in the following priority:

1. From your package.json

If you have a package.json file in the current directory, you can add an extra "stylelint-teamcity-reporter" property to it:

{
  "stylelint-teamcity-reporter": {
    "reporter": "inspections"
  }
}

2. ENV variables

export STYLELINT_TEAMCITY_REPORTER="inspections"