Home
Docs
GitHub
Pricing
Blog
Log In

Run Sandworm Audit for your App

Get started
Hold on, we're currently generating a fresh version of this report
Generated on May 7, 2024 via pnpm

@eslint/js 8.56.0

ESLint JavaScript language implementation
Package summary
Share
0
issues
1
license
1
MIT
Package created
31 Jan 2023
Version published
15 Dec 2023
Maintainers
2
Total deps
1
Direct deps
0
License
MIT

Issues

0
This package has no issues

Licenses

MIT License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
sublicense
private-use
Cannot
hold-liable
Must
include-copyright
include-license
1 Packages, Including:
@eslint/js@8.56.0
Disclaimer

This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.

Sandworm is not a law firm and does not provide legal services. Distributing, displaying, or linking to this deed or the license that it summarizes does not create a lawyer-client or any other relationship.

Direct Dependencies

0
All Dependencies CSV
ⓘ This is a list of @eslint/js 's direct dependencies. Data on all dependencies, including transitive ones, is available via CSV download.
NameVersionSizeLicenseTypeVulnerabilities

Visualizations

Frequently Asked Questions

What does @eslint/js do?

The @eslint/js is a useful npm package that offers JavaScript-specific functionalities. Born out of the need to separate these functionalities from ESLint, @eslint/js provides two major configurations:

  1. recommended - This configuration comprises rules that are highly recommended by the ESLint team. This is essentially a replacement for "eslint:recommended".
  2. all - This configuration enables all ESLint rules and it serves as a replacement for "eslint:all".

These configurations grant you the ability to improve the quality of your JavaScript codebase and adhere to the best practices recommended by the experienced ESLint team.

How do you use @eslint/js?

The usage of @eslint/js is straightforward and well-documented. You start by installing it in your project using npm. The installation command is npm install @eslint/js -D. Once it is installed, you can use the configurations in your eslint.config.js file.

Here are a few examples of how you can use the @eslint/js configurations in your project:

To apply recommended rules to JavaScript files, you would write:

import js from "@eslint/js";

export default [
    {
        files: ["**/*.js"],
        rules: js.configs.recommended.rules
    }
]

You can also apply recommended rules with an override as follows:

import js from "@eslint/js";

export default [
    {
        files: ["**/*.js"],
        rules: {
            ...js.configs.recommended.rules,
            "no-unused-vars": "warn"
        }
    }
]

To apply all rules to your JavaScript files, the code would look something like this:

import js from "@eslint/js";

export default [
    {
        files: ["**/*.js"],
        rules: {
            ...js.configs.all.rules,
            "no-unused-vars": "warn"
        }
    }
]

Please note that you can change the rules according to your project’s requirements.

Where are the @eslint/js docs?

The documentation for the @eslint/js module is easily available on the ESLint website. The configurational aspects of ESLint can be found here, while a list of the rules it provides can be reviewed here.

To contribute to the development and improvement of @eslint/js, you can check out the contribution guide here. Remember, every little bit helps in making this module more powerful and user-friendly.