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

@skodaflow/eslint-formatter-junit

v1.0.1

Published

ESLint formatter for JUNIT report format with custom improvements

Downloads

507

Readme

eslint-formatter-junit

JUNIT formatter for ESLint rules report. Original source code is taken over ESLINT repository which is licensed under MIT, so free to modify and reuse. This version can be improved and modified for purpose of Skoda Auto projects. Formatter is very useable espacially in combination with @skodaflow/eslint-config-react. Use this formatter for better results in Azure DevOpps pipeline > Publish Test Results task

Installation

You need to have accecss to registry: https://devops.skoda.vwgroup.com/projects/WFA/_packaging/skodaflow-npm/npm/registry/

npm install --save-dev @skodaflow/eslint-formatter-junit

Usage

Run eslint command with two arguments: -f define formatter, -o define output file name. The last arguments is folder with source code to lint.

eslint -f @skodaflow/eslint-formatter-junit -o eslint/results/LINT-web-library.xml src

Output

eslint/results/LINT-web-library.xml

<?xml version="1.0" encoding="utf-8"?>
<testsuites>
<testsuite package="org.eslint" time="0" tests="1" errors="1" name="c:\Projects\SKODAFLOW\Flow_WebLibrary\packages\web-library\src\components\button\button.tsx">
<testcase time="0" name="org.eslint.prettier/prettier" classname="c:\Projects\SKODAFLOW\Flow_WebLibrary\packages\web-library\src\components\button\button"><failure message="Insert `;`"><![CDATA[at c:\Projects\SKODAFLOW\Flow_WebLibrary\packages\web-library\src\components\button\button.tsx, line 51, col 3, Error - Insert `;` (prettier/prettier)]]></failure></testcase>
</testsuite>

CI/CD

  1. Run eslint via NPM in pipeline to report issues as junit file
  2. Use "Publish Test Results" task to show report in build overview.
  3. Use JUNIT as Test result format
  4. and **/LINT-*.xml as Test Results Files
  5. from $(System.DefaultWorkingDirectory) Search folder