npmpackage.info

@financial-times/eslint-config-next

ESLint configuration for Next projects

7.1.0

MIT

JavaScript

Installations

npm install @financial-times/eslint-config-next

Pull Requests

Open

8

Total

38

Closed

4

Merged

26

Issues

Open

0

Total

0

Closed

0

Releases

v7.1.0 Add support for Node 18

v7.1.0

Published on 15 Jun 2023

v7.0.0

Published on 17 Apr 2023

v6.0.0: Upgrade ecmaVersion 2018 -> 2020

v6.0.0

Published on 12 Sept 2022

v5.0.0

Published on 11 Aug 2022

v4.0.0: Overdue maintenance release

v4.0.0

Published on 21 Mar 2022

v3.0.0: Upgrade to Node v12

v3.0.0

Published on 14 Oct 2020

View all 10 releases

Developer

Financial-Times

Developer Guide

BETA

Module System

Unable to determine the module system for this package.

Min. Node Version

16.x || 18.x

Typescript Support

No

Node Version

18.16.0

NPM Version

9.5.1 Statistics

1 Stars

70 Commits

1 Forks

41 Watching

9 Branches

27 Contributors

Updated on 16 Oct 2024

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

345,259

Last day

277.9%

684

Compared to previous day

Last week

-31.4%

3,976

Compared to previous week

Last month

213.7%

13,327

Compared to previous month

Last year

-44.1%

54,214

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

eslint eslint-plugin-no-only-tests

Dev Dependencies

@financial-times/n-gage check-engine

Versions

eslint-config-next

ESLint configuration for Next projects

Usage

Reference the shared configuration in your repository's own .eslintrc.js like so:

1module.exports = {
2	extends: ['@financial-times/eslint-config-next']
3}

Avoid using .eslintrc file format since it has been depracated.

You can find the docs for ESLint shareable configs here.

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

7

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

4

Maintained

Determines if the project is "actively maintained".

3

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

SAST

Determines if the project uses static code analysis.

Score

4.1

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More

Other packages similar to @financial-times/eslint-config-next

eslint-plugin-compat

6.0.1

Lint browser compatibility of API used

@rushstack/eslint-patch

1.10.4

Enhance ESLint with better support for large scale monorepos

@dotcom-reliability-kit/eslint-config

3.1.1

A linting config, specifically focussed on enhancing code quality and proactively catching errors/bugs before they make it into production

eslint-config-prettier

9.1.0

Turns off all rules that are unnecessary or might conflict with Prettier.