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

eslint-formatter-gitlab-nx

v1.0.2

Published

Show ESLint results directly in the GitLab code quality results (in nx.dev workspace)

Downloads

9

Readme

ESLint Formatter for GitLab (NX)

Show ESLint results of an NX workspace directly in the GitLab code quality results

Requirements

This requires at least GitLab Bronze or Starter 11.5 and at least ESLint 5.

Installation

Expects an NX workspace that is setup with eslint.

Expects projects to have a lint target.

"lint": {
  "executor": "@nrwl/linter:eslint",
  "outputs": ["{options.outputFile}"],
  "options": {
    "lintFilePatterns": ["apps/graphql/**/*.{ts,tsx,js,jsx}"],
    "format": "gitlab-nx"
  }
}

Define a GitLab job to run nx lint.

.gitlab-ci.yml:

nx:lint:
  stage: test
  only:
    - merge_request
  variables:
    ESLINT_CODE_QUALITY_REPORT: gl-codequality.json
  before_script:
    - apk add --update --no-cache bash git jq
    - git fetch
  script:
    - yarn nx affected --target=lint --base=origin/$CI_MERGE_REQUEST_TARGET_BRANCH_NAME
  after_script:
    - |
      # merge individual reports into single file
      find tmp -name "$ESLINT_CODE_QUALITY_REPORT"
      touch "$ESLINT_CODE_QUALITY_REPORT"
      find tmp -name "$ESLINT_CODE_QUALITY_REPORT" -print0 |
      while IFS= read -r -d '' f; do
          echo "$( jq -c '.[]' "$f" )" >> "$ESLINT_CODE_QUALITY_REPORT"
      done
      echo "$( jq -s '.' "$ESLINT_CODE_QUALITY_REPORT" )" > "$ESLINT_CODE_QUALITY_REPORT"
  artifacts:
    reports:
      codequality: gl-codequality.json

The formatter will automatically detect a GitLab CI environment. It will detect where to output the code quality report based on the GitLab configuration file.

Example

An example of the results can be seen in Merge Request !1 of eslint-formatter-gitlab itself.

Configuration Options

ESLint formatters don’t take any configuration options. In order to still allow some way of configuration, options are passed using environment variables.

| Environment Variable | Description | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | ESLINT_CODE_QUALITY_REPORT | The name of code quality report. By default it will detect the location of the codequality artifact defined in the GitLab CI configuration file. |

Upgrading

to v3

  • Support for the environment variable ESLINT_FORMATTER has been removed, console output now always uses a builtin formatter.