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 🙏

© 2025 – Pkg Stats / Ryan Hefner

eslint-config-lexmarkweb

v0.1.6

Published

ESLint configuration for Lexmark Web Team

Downloads

18

Readme

eslint-config-lexmarkweb

ESLint config for Lexmark web team

Introduction

ESLint provides static code analysis for Javascript. It looks through your code and makes sure it conforms to standards. The rules here are the standards for the Lexmark Global Web Team.

Getting Started

We assume Mac users have homebrew installed already. Windows and Linux users follow a similar process.

  1. Install nodejs brew install node
  2. Install eslint npm install -g eslint eslint-config-lexmarkweb
  3. Create a file in your home directory ~/.eslintrc that contains extends: lexmarkweb

Integration

AFTER following the Getting Started instructions above, here is how you use ESLint.

  • Command line

    1. From commandline type eslint file.js
    2. To fix issues automatically you can type eslint --fix file.js. The file.js will be modified directly.
  • Atom

    1. From Atom | Preferences... | Packages search for linter-eslint
    2. Install the package
    3. Package Settings
    • Set Global Node Installation Path to /usr/local
    • Set Use global ESLint installation
    1. When you open a Javascript file errors will be highlighted.
  • IntelliJ

    1. From IntelliJ Idea | Preferences | Plugins click Browse repositories... and search for ESLint.
    2. Restart IntelliJ
    3. From IntelliJ Idea | Preferences | Other Settings | ESLint
    • Check enable
    • Set Node interpretter to /usr/local/bin/node
    • Set Path to eslint bin to /usr/local/bin/eslint
    • Select Let eslint search for .eslint up the folder tree
    1. When you open a Javascript file errors will be highlighted.
  • SublimeText

    1. Choose Tools | Install Package Control... if you have not done that already.
    2. From Tools | Command Pallette type install and select Package control: Install Package
    3. Type SublimeLinter and install the SublimeLinter package.
    4. From Tools | Command Pallette type install and select Package control: Install Package
    5. Type contrib-eslint and install the submlimelinter-contrinb-eslint package.
    6. When you open a Javascript file errors will be highlighted.
  • VisualStudio Code

    1. Ctrl-Shift-X and find and install the ESLint plugin by Dirk Baeumer.
    2. When you open a Javascript file errors will be highlighted.
  • VIM. If you use VIM you don't need step by step instructions. :wink:

See the ESLint site for other integrations