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

@hesamse/eslint-plugin-recommended

v1.0.1

Published

An ESLint plugin with custom rules for TypeScript projects, including a rule to enforce the presence of JSX elements in `.tsx` files. Ideal for projects using React with TypeScript.

Downloads

139

Readme

@hesamse/eslint-plugin-recommended

An ESLint plugin with custom rules for TypeScript projects, including a rule to enforce the presence of JSX elements in .tsx files. Ideal for projects using React with TypeScript.

Features

  • no-tsx-without-jsx: Enforces that .tsx files contain JSX elements. If a .tsx file does not include any JSX, this rule will report an error, encouraging you to use the correct file extensions (.ts instead of .tsx when JSX is not used).

Installation

First, install the plugin using npm:

npm install --save-dev @hesamse/eslint-plugin-recommended

Or with yarn:

yarn add --dev @hesamse/eslint-plugin-recommended

Usage

To use this plugin, include it in your ESLint configuration:

eslint.config.js

If you are using eslint.config.js:

import hesamseRecommended from '@hesamse/eslint-plugin-recommended';

export default {
  parser: '@typescript-eslint/parser',
  plugins: {
    '@hesamse/recommended': hesamseRecommended,
  },
  rules: {
    '@hesamse/recommended/no-tsx-without-jsx': 'error',
  },
  overrides: [
    {
      files: ['**/*.tsx'],
      rules: {
        '@hesamse/recommended/no-tsx-without-jsx': 'error',
      },
    },
  ],
};

.eslintrc.json (if you still prefer JSON configuration)

{
  "parser": "@typescript-eslint/parser",
  "plugins": ["@hesamse/recommended"],
  "rules": {
    "@hesamse/recommended/no-tsx-without-jsx": "error"
  },
  "overrides": [
    {
      "files": ["**/*.tsx"],
      "rules": {
        "@hesamse/recommended/no-tsx-without-jsx": "error"
      }
    }
  ]
}

Rule: no-tsx-without-jsx

What does it do?

The no-tsx-without-jsx rule ensures that files with a .tsx extension contain at least one JSX element. This helps maintain consistency in your project by enforcing the use of .tsx files only when necessary. If no JSX is present, consider renaming the file to .ts.

Example

✅ Valid

// myComponent.tsx
import React from 'react';

const MyComponent = () => <div>Hello, World!</div>;

export default MyComponent;

❌ Invalid

// myUtility.tsx
export function myUtilityFunction() {
  return 42;
}

The above code would trigger an error, suggesting that the file should be renamed to .ts since no JSX is present.

Contributing

Contributions are welcome! If you want to add new rules or improve existing ones, feel free to fork the repository and open a pull request.

License

MIT © hesamSe