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

@ctlyst-test/eslint-config

v0.0.13

Published

ESLint config used at ctlyst.id

Downloads

8

Readme

ctlyst-eslint-config

ESLint config used at ctlyst.id

This is the common ESLint config used by projects at ctlyst.id.

Installation

Install eslint and @ctlyst-test/eslint-config using your favourite package manager:

# yarn
yarn add --dev eslint @ctlyst-test/eslint-config
# npm
npm install --save-dev eslint @ctlyst-test/eslint-config

Then, in your .eslintrc file, extend @ctlyst-test/eslint-config.

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

If you're using this ESLint config for React-based projects, extend @ctlyst-test/eslint-config/react instead.

{
  "extends": ["@ctlyst-test/eslint-config/react"]
}

If you're using this ESLint config for next.js projects, extend @ctlyst-test/eslint-config/next instead.

{
  "extends": ["@ctlyst-test/eslint-config/next"]
}

For more setups, take a look at the templates directory

Versioning

Note that this package does not specifically follow Semantic Versioning, since all changes in this package are relative to the changes in our Development Standard. Major version bumps will occur when we transition into a new major version of ESLint.

To recap:

  • major: Will be bumped when we transition to a new major version of ESLint
  • minor: Potentially breaking changes that's still within the same major version of ESLint
  • patch: Minor patches/bugfixes

Using TypeScript

To use @ctlyst-test/eslint-config with TypeScript, you need to do a little additional setup to make eslint-plugin-import play well with TypeScript. First, install eslint-import-resolver-typescript.

# yarn
yarn add --dev eslint-import-resolver-typescript

Then, on .eslintrc:

module.exports = {
  // other configuration are omitted for brevity
  settings: {
    'import/resolver': {
      typescript: {}, // this loads <rootdir>/tsconfig.json to eslint
    },
  },
};

Using Prettier

Prettier is a tool to automatically format your code during save. It supports various editors, from VSCode, Atom, Sublime, and even Emacs.

To use this ESLint config in conjunction with Prettier, copy the .prettierrc file in this repository and paste it to your project.

Then install the Prettier eslint config and plugin:

$ yarn add --dev eslint-plugin-prettier eslint-config-prettier prettier

And finally, include them as follows. (IMPORTANT: eslint-config-prettier MUST be extended after @ctlyst-test/eslint-config!)

{
  "extends": ["@ctlyst-test/eslint-config", "prettier", "prettier/@typescript-eslint", "plugin:prettier/recommended"],
  "plugins": ["prettier"],
  "rules": {
    "prettier/prettier": "error"
  }
}

Contributing

Issues and Pull Requests welcome! Please read the Contributing Guidelines beforehand.

License

MIT (c) ctlyst.id

Maintainers

  • Fahmi Idris – ctlyst.id