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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@marinade.finance/eslint-config

v1.3.1

Published

Shared ESLint configuration for TypeScript/NodeJS/React/Next.js projects

Downloads

387

Readme

Marinade ESLint and Prettier Configuration

Shared configuration for ESLint and Prettier used in Marinade projects.

How to Use

1. Configure package.json

Update the package.json of the dependent project to include the required dependencies and recommended scripts:

{
  "name": "@marinade.finance/project-name",
  "scripts": {
    ...
    "lint:ts": "eslint .",
    "lint:ts-fix": "eslint . --fix",
    "lint": "pnpm run lint:ts",
    "lint:fix": "pnpm run lint:ts-fix",
    "format": "prettier --write .",
    "format:check": "prettier --check .",
    "check": "pnpm lint && pnpm format:check",
    "fix": "pnpm lint:fix && pnpm format",
    "prepare": "husky",
    ...
  },
  "devDependencies": {
    "@marinade.finance/eslint-config": "1.2.1",
    "eslint": "^9.33.0",
    "prettier": "^3.6.2",
    ...
  }
}

Then run pnpm install.

2. Create eslint.config.cjs

Create an eslint.config.cjs file in the root of your project (next to package.json). You can use the configuration as is, or customize it as needed:

const createSharedConfig = require('@marinade.finance/eslint-config')

const sharedConfig = createSharedConfig({})

module.exports = [
  ...sharedConfig,
  {
    rules: {
      'no-console': 'off',
    },
  },
  {
    files: ['**/*.spec.ts'],
    rules: {
      '@typescript-eslint/no-unsafe-member-access': 'off',
    },
  },
]

3. Create prettier.config.js

Create a prettier.config.js file in the root of your project:

module.exports = require('@marinade.finance/eslint-config/prettier')

To customize Prettier settings

module.exports = {
  ...require('@marinade.finance/eslint-config/prettier'),
  // additional prettier options
  printWidth: 100,
}

3.b. (Optional) Create .prettierrc file

To exclude files from Prettier formatting, create a .prettierignore file with entries like:

node_modules/
dist/
build/
target/
out/

*.tsbuildinfo
pnpm-lock.yaml

.DS_Store
.vscode/
.idea/

4. (Optional) Set Up Husky

You can use Husky to automatically run linting and formatting before commits.

Run:

npx husky-init

This sets up a .husky directory and a pre-commit hook. It also adds a prepare script to package.json.

In .husky/pre-commit, you can use:

pnpm check