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

@optimics/eslint-config

v0.8.0

Published

ESLint configuration for Optimics devs

Downloads

211

Readme

Optimics eslint preset

Installation

npm install --save-dev @optimics/eslint-config @babel/preset-env @babel/eslint-parser

Project configuration

Add @babel/preset-env to your .babelrc.json in the root of your project if you don't already have it.

{
  "presets": [
    ["@babel/preset-env"]
  ]
}

Add @optimics/eslint-config to your .eslintrc.json in the root of your project if you don't already have it.

{
  "extends": [
    "@optimics/eslint-config"
  ]
}

A couple of features might be useful to you. Consider the environment your application is running in and maybe enable some of these in your .eslintrc.json. Always turn on only what is needed, don't think into the future.

  • browser to enable web browser features, like window, document, etc
  • es6 is always useful when using newer versions of ECMAScript
  • jest when testing in Jest framework
  • node when running code in Node.js
{
  "env": {
    [YOUR-FEATURE]: true
  }
}

Editor configuration

vim

Assuming, you have dense-analysis/ale installed, you only need to turn on eslint as your linter and fixer.

let g:ale_fix_on_save = 1
let g:ale_fixers = {'javascript': ['eslint']}
let g:ale_linters = {'javascript': ['eslint']}

This little trick will also make your .vimrc compatible with other linters. Enable all of your linters and fixers and disable them as needed based on the specific project requirements.

This bit will turn on eslint only for javascript files and only if it finds a file starting with .eslintrc.

let g:ale_fix_on_save = 1

function OhMyGlobItIsJavascript()
  if glob('.eslintrc*', '.;') != ''
    let g:ale_linters = { 'javascript': [ 'eslint' ] }
    let g:ale_fixers = { 'javascript': [ 'eslint' ] }
  endif
endfunction

autocmd FileType javascript call OhMyGlobItIsJavascript()

Atom

Install the linter-eslint-node extension.

apm install https://github.com/AtomLinter/linter-eslint-node

Unfortunately, the good old linter-eslint cannot handle eslint-8, so this is a quick fix.

Don't forget to turn on fix on save by adding this into your config.cson file.

  "linter-eslint-node":
    autofix:
      fixOnSave: true

vscode

Install the ESlint extension and add this into our settings.json file:

{
  "editor.formatOnSave": true,
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": true
  }
}