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

@lokalise/eslint-config-lokalise-frontend

v1.0.3

Published

Shareable eslint config for frontend codebases

Downloads

29

Readme

eslint-config-lokalise-frontend

Shareable eslint config for frontend codebases

Using this config

Install the config in your repo:

npm add -D eslint @lokalise/eslint-config-lokalise-frontend

Then add the following to .eslintrc.json in the root of your project:

{
  "extends": "@lokalise/eslint-config-lokalise-frontend"
}

Finally add a package script in your package.json as follows:

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

Feel free to customize the --ext CLI arg according to your project needs.

Note that this shareable config needs to know where your tsconfig is located in order to be able to parse TypeScript code. By default it will assume that your tsconfig is in the same directory as your eslint config. If that's the case, it'll work without any additional configuration. However if that is not the case, you will need to explicitly tell it where the tsconfig in your repo is. For example:

{
  "extends": "@lokalise/eslint-config-lokalise-frontend",
  "parserOptions": {
    "project": "../tsconfig.json"
  }
}

Modular Configuration

The default config assumes that you have a stack including:

  • TypeScript
  • React
  • Jest

However you can pick and choose just the parts you like.

The following modular configs are available:

  • @lokalise/eslint-config-lokalise-frontend/core
  • @lokalise/eslint-config-lokalise-frontend/typescript
  • @lokalise/eslint-config-lokalise-frontend/react
  • @lokalise/eslint-config-lokalise-frontend/jest

We recommend you always pick core, but suppose the only other one you need is typescript, then you would add the following to your eslint config:

{
  "extends": [
    "@lokalise/eslint-config-lokalise-frontend/core",
    "@lokalise/eslint-config-lokalise-frontend/typescript"
  ]
}