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

@lint-suite/eslint-plugin-no-inline-return-object

v1.0.0

Published

Require returned object literals to be named first

Readme

@lint-suite/eslint-plugin-no-inline-return-object

An ESLint rule for JavaScript and TypeScript that requires directly returned object literals to be named first. It makes returned values easier to inspect and reuse by reporting object literals in return statements and expression-bodied arrow functions.

Compatibility

Requires ESLint ^10.9.1 and TypeScript >=6.0.3. The package is built and tested with Node.js 24.

Installation

pnpm add -D @lint-suite/eslint-plugin-no-inline-return-object eslint@^10.9.1 typescript@^6.0.3 typescript-eslint@^8.69.0

Configuration

The plugin does not configure a parser. This flat config parses the TypeScript examples below:

import plugin from '@lint-suite/eslint-plugin-no-inline-return-object';
import tseslint from 'typescript-eslint';

export default [
  {
    files: ['**/*.ts'],
    languageOptions: { parser: tseslint.parser },
    plugins: { 'no-inline-return-object': plugin },
    rules: { 'no-inline-return-object/no-inline-return-object': 'error' }
  }
];

Options

This rule has no options.

Scope and exemptions

The rule reports only an ObjectExpression returned directly by a return statement or by an expression-bodied arrow function. It does not report named results, primitive values, array expressions, object literals that are merely assigned, or object literals nested inside another returned expression. Every report includes a suggestion that introduces a const result.

Examples

Each snippet below is checked by this rule alone, not by an entire ESLint configuration.

Valid examples

1. Return a named result

function create() {
  const result = { ok: true };

  return result;
}

2. Arrow returns a named result

const create = () => {
  const result = { ok: true };

  return result;
};

3. Primitive return value

function status(): number {
  return 200;
}

4. Array expression return value

const ids = () => [1, 2, 3];

5. Assigned object that is not returned

const result = { ok: true };
void result;

Invalid examples

1. Object literal in a function return

function create() {
  return { ok: true };
}

Name the object before returning it.

2. Empty object literal in a return

function create() {
  return {};
}

Name the empty object before returning it.

3. Object literal in an arrow block return

const create = () => {
  return { ok: true };
};

Name the object before returning it.

4. Object literal arrow expression body

const create = () => ({ ok: true });

Use a block body with a named result and an explicit return.

5. Nested arrow expression body

class Factory {
  create() {
    return () => ({ ok: true });
  }
}

The expression-bodied inner arrow returns an object literal directly.

The named noInlineReturnObjectRule export is for composed plugin registries.