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

@osedea/eslint-config

v7.1.0

Published

ESLint configuration for Osedea projects.

Downloads

69

Readme

eslint config osedea

Peer dependencies

eslint >= 7.30 is a requirement. See external dependencies list below.

Configuring rules for project

@osedea/eslint-config comes with the following environments, some of which are already pre-configured, however you can mix-and-match the environments if you want.

Config name | Extends | External Dependencies (besides eslint) ----------------| ---------- | ------ cypress | | cypress es5 | | esnext | es5 | flow | | flow-bin jest | | jest, jest-dom, testing-library mocha | | mocha node | esnext, mocha | prettier | | prettier react | esnext | react-native | react | typescript | esnext | typescript

Create a file called .eslintrc.yml in the root of your project. Here, you will specify your rules, and extend one (or more) of the above rulesets.

Some example .eslintrc.yml configs:

extends:
  - '@osedea/eslint-config/react' # extends other configs, see above
  - '@osedea/eslint-config/typescript'
  - '@osedea/eslint-config/prettier' # always needs to be last
extends:
  - '@osedea/eslint-config/react-native' # extends other configs, see above
  - '@osedea/eslint-config/flow'
  - '@osedea/eslint-config/prettier' # always needs to be last
extends:
  - '@osedea/eslint-config/node' # extends other configs, see above
extends:
  - '@osedea/eslint-config/es5'
  - '@osedea/eslint-config/angular'

# You can override rules from the linter here. Use at your own risk.
# rules:
#   comma-dangle: off # For example, if you do not want the linter to check for dangling commas ever

Global settings

Depending on your config, you may need to add a settings block to your .eslintrc.yml.

osedea/typescript

Add this block to your eslintrc:

parserOptions:
  project: './tsconfig.json'

If using VSCode & eslint errors aren't displaying, add this to your settings.json:

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

osedea/react-native

For react-native config, in order to resolve imports (import x from CoolProject/.../...), the project name must be defined. The plugin will use the name param of the package.json in order to solve this.

{
  "name": "CoolProject",
  ...
}

osedea/node

For node config, it uses the engines section of package.json:

{
  ...
  engines: {
    "node": ">= 6.0.0"
  },
  ...
}

osedea/prettier

Needs to be added last so it is able to override other configs.

osedea/import

If you're using webpack to alias your directories, you can fix this by installing eslint-import-resolver-webpack and adding to your project's eslintrc:

settings:
  import/resolver: webpack

osedea/flow

Use a flow plugin for your editor (for example, flow language support for VSCode). Otherwise using eslint-plugin-flowtype-errors is an option.