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

@merkle-open/eslint-config

v4.0.0

Published

Default configurations for eslint

Downloads

1,012

Readme

ESLint config

Build Status npm Codestyle

Installation

$ npm install --save-dev eslint eslint-plugin-import @merkle-open/eslint-config

Usage Typescript (recommended)

  • @merkle-open/eslint-config/configurations/typescript-browser - typescript + browser
  • @merkle-open/eslint-config/configurations/typescript-react - typescript + react
  • @merkle-open/eslint-config/configurations/typescript-node - typescript + node

package.json

{
  "scripts": {
    "lint:ts": "eslint . --ext .jsx,.js,.ts,.tsx"
  }
}

Enabling ESLint on TS files in VSCode

You need to update the eslint.validate setting to:

"eslint.validate": [
  "javascript",
  "javascriptreact",
  "typescript",
  "typescriptreact"
]

Usage ES8 (ES2017)

  • @merkle-open/eslint-config/configurations/es8-browser - ES8 + browser
  • @merkle-open/eslint-config/configurations/es8-react - ES8 + react
  • @merkle-open/eslint-config/configurations/es8-node - ES8 + node

Usage ES7 (ES2016)

  • @merkle-open/eslint-config/configurations/es7-browser - ES7 + browser (deprecated)
  • @merkle-open/eslint-config/configurations/es7-react - ES7 + react (deprecated)
  • @merkle-open/eslint-config/configurations/es7-node - ES7 + node

Usage ES6 (ES2015) - deprecated

  • @merkle-open/eslint-config/configurations/es6-browser - ES6 + browser (deprecated)
  • @merkle-open/eslint-config/configurations/es6-react - ES6 + react (deprecated)
  • @merkle-open/eslint-config/configurations/es6-node - ES6 + node (deprecated)

Usage with Prettier

.eslintrc.js (add globals here if needed)

module.exports = {
  extends: require.resolve('@merkle-open/eslint-config/configurations/es8-browser.js'),
};

.eslintignore

/.idea/
/node_modules/

package.json

"scripts": {
  "lint": "npm run lint:js",
  "lint:js": "eslint ."
},

then run npm run lint

Example usage in project tree

  • .eslintrc.js (es8-react)
  • .eslintignore
  • src
    • app.jsx
  • test
    • .eslintrc.js (es8-node)
    • index.js
  • scripts
    • .eslintrc.js (es6-node)
    • index.js

Documentation

Build release

  1. Create feature or bugfix branch based on master
  2. Make changes and create pull request, add reviewer, wait for approval
  3. Merge pull request into master
  4. Prepare release notes, adjust package.json to next version ([Semantic Versioning](semantic versioning))
  5. Run npm publish (locally) to create npm version
  6. Create and push git tag for version
  7. Add release notes on GitHub

Thanks to

License

MIT License

Changelog

Please see the Releases