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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@dcl/eslint-config

v3.1.0

Published

Decentraland ESLint config

Readme

DCL ESLint & Prettier Config

Installation

# Using Yarn
yarn add -D @dcl/eslint-config

# Using npm
npm install -D @dcl/eslint-config

Prerequisites

  • Node.js >= 18.18.0
  • ESLint >= 9.0.0
  • TypeScript (for TypeScript-based presets)

Usage (ESLint 9, eslint.config.js)

In your eslint.config.js:

const coreDapps = require("@dcl/eslint-config/core-dapps.config");

module.exports = [...coreDapps];

Other presets available:

  • @dcl/eslint-config/core-services.config
  • @dcl/eslint-config/dapps.config
  • @dcl/eslint-config/ui.config
  • @dcl/eslint-config/sdk.config

Legacy usage with .eslintrc (ESLint 8 / transition)

In your .eslintrc.cjs:

module.exports = {
  extends: ["@dcl/eslint-config/core-dapps"],
};

Type-aware rules without manual parserOptions.project

TypeScript presets (for example core-dapps) auto-detect a tsconfig in the consumer repo:

  • tsconfig.eslint.json (preferred)
  • tsconfig.json
  • tsconfig.app.json / tsconfig.node.json (Vite)

If no tsconfig is found, rules that require type information are disabled to avoid crashes.

npm-package-json-lint (shareable config)

In your .npmpackagejsonlintrc.json:

{
  "extends": "@dcl/eslint-config/npm-package-json-lint"
}

Key rules:

  • dependencies and devDependencies must use exact versions
  • automatic exception (computed from your package.json): internal packages (@dcl/*, decentraland-*) may use version ranges (^)

How the exception works:

  • @dcl/eslint-config/npm-package-json-lint is a JavaScript config module.
  • When npmPkgJsonLint loads it, it reads the consumer repo package.json from process.cwd() and builds the exception list from the package names found in dependencies/devDependencies that match @dcl/* or decentraland-*.
  • That means you don't need to list exceptions manually: if you add @dcl/schemas with ^ it will be allowed; if you add react with ^ it will be reported.

Monorepos: run npmPkgJsonLint from the package folder you want to lint (so process.cwd() points to the right package.json), or override rules locally.

Peer dependencies

This package publishes most tooling as peerDependencies. In the consumer repo you'll need (depending on the preset):

  • eslint
  • @typescript-eslint/parser, @typescript-eslint/eslint-plugin
  • prettier, eslint-plugin-prettier, eslint-config-prettier
  • eslint-plugin-import, eslint-import-resolver-typescript
  • eslint-plugin-react (if you use React presets)
  • eslint-plugin-autofix

Note: some presets configure the babel-module resolver; if you use it, install eslint-import-resolver-babel-module and its peers (@babel/core, babel-plugin-module-resolver).

Upgrading from v2 to v3

Breaking changes

  • ESLint 9 required – The new flat config (eslint.config.js) requires ESLint >= 9.0.0
  • Peer dependencies – Plugins are now peer dependencies (you install them in your project)
  • New entrypoints – Use *.config.js for ESLint 9, keep * (without .config) for legacy .eslintrc
  • Removed presetsgatsby preset has been removed

Migration steps

  1. Update the package:
# Yarn
yarn add -D @dcl/eslint-config@^3.0.0

# npm
npm install -D @dcl/eslint-config@^3.0.0
  1. Install peer dependencies (if not already present):
# Yarn
yarn add -D eslint @typescript-eslint/parser @typescript-eslint/eslint-plugin \
  prettier eslint-plugin-prettier eslint-config-prettier \
  eslint-plugin-import eslint-import-resolver-typescript eslint-plugin-autofix

# npm
npm install -D eslint @typescript-eslint/parser @typescript-eslint/eslint-plugin \
  prettier eslint-plugin-prettier eslint-config-prettier \
  eslint-plugin-import eslint-import-resolver-typescript eslint-plugin-autofix
  1. Update your ESLint config:
// eslint.config.js (ESLint 9)
const coreDapps = require("@dcl/eslint-config/core-dapps.config");

module.exports = [...coreDapps];
  1. If you encounter peer dependency conflicts:
# Yarn - Remove conflicting old versions first
yarn remove eslint @typescript-eslint/parser @typescript-eslint/eslint-plugin

# Then reinstall with exact versions
yarn add -D [email protected] @typescript-eslint/[email protected] @typescript-eslint/[email protected]
# npm - Remove conflicting old versions first
npm uninstall eslint @typescript-eslint/parser @typescript-eslint/eslint-plugin

# Then reinstall with exact versions
npm install -D [email protected] @typescript-eslint/[email protected] @typescript-eslint/[email protected]

Note: Avoid using --legacy-peer-deps unless absolutely necessary, as it can mask version incompatibilities.

License

Apache 2.0