eslint-plugin-check-file

Added

• support flat config for ESLint v9.0.0

Fixed

• the rule filename-blocklist can set the suggested glob pattern as empty string when errorMessage is set (#36)

Thanks @AtlasTom (#34)

Added

• the rule filename-naming-convention can set errorMessage property to customize the error message
• the rule filename-blocklist can set errorMessage property to customize the error message

Changed

• Node.js version should >= 18

Thanks @leepowellnbs (#31)

Fixed

• the naming convention NEXT_JS_APP_ROUTER_CASE can support Next.js Private Folders

Fixed

• fix bundle mistake in v2.6.0

This version has been deprecated. Please use the latest version.

Added

• added ES Module support

Deprecated

• deprecated Node.js 14 support

Node.js 14 support will be removed in next major version.

Thanks to @milos-sikic-nimbus-tech

Added

• the rule folder-naming-convention can be used with a new built-in naming convention NEXT_JS_APP_ROUTER_CASE

NEXT_JS_APP_ROUTER_CASE is useful for Next.js App Router projects. Click here to learn more.

Fixed

• the rule folder-naming-convention can work well with * in the glob #25

Added

• the rule no-index can ignore middle extensions #26

Changed

• improve documentation

Fixed

• the rule folder-naming-convention can use a pattern with multiple matchers to select target folders #21

Added

• the rule filename-blocklist should report an error when blocklist pattern object isn't an object type
• the rule filename-naming-convention should report an error when naming pattern object isn't an object type
• the rule folder-match-with-fex should report an error when naming pattern object isn't an object type
• the rule folder-naming-convention should report an error when naming pattern object isn't an object type

Changed

• unify the style of error messages for the existing rules
• upgrade dependencies to the latest version

Thanks to @ratierd #17

Added

• the rule filename-naming-convention can use prefined match syntax

Thanks to @jbkey23 #18

Fixed

• the rule filename-blacklist can specify the target file by its file path

Deprecated

• the rule filename-blacklist can specify the target file by its filename

Thanks to @jbkey23 #16

Changed

• the rule filename-blacklist renamed to filename-blocklist
• the rule filename-naming-convention show filename without path in error message

Removed

• the rule filename-naming-convention can specify the target file by its extension

In this version, there have been some incompatible changes. Here is what you need to know:

• the rule filename-blacklist need to renamed to filename-blocklist
• the rule filename-naming-convention cann't specify the target file by its extension any more. Please select your target files by their file path. For example, using **/*.js instead of *.js to select all js files.

Fixed

• fix builtin CAMEL_CASE glob expression #14

Thanks to @florianehmke #11

Added

• the rule filename-blacklist can blacklist file names by pattern

Fixed

• fix builtin SNAKE_CASE, KEBAB_CASE and SCREAMING_SNAKE_CASE glob expressions

Changed

• reduce npm package size

Fixed

• enhance support for the Windows operating system

Added

• add CHANGELOG

Changed

• add Windows operation system support

Fixed

• fix get wrong folder issue when eslint is worked with processors

New Feature

• the rule filename-naming-convention can specify the target file by its file path
• the rule filename-naming-convention can set ignoreMiddleExtensions property to ignore middle extensions when matching naming pattern

Others

• optimize docs

Please Note: When using the rule filename-naming-convention, please specify the target file by its file path, the compatible feature of specifying the target file by extension will be removed in the future.

Add 1 rule:

• check-file/folder-naming-convention: Enforce a consistent naming pattern for the name of the specified folder

Add 3 rules:

• check-file/folder-match-with-fex: Enforce a consistent naming pattern for the folder of the specified file extension
• check-file/filename-naming-convention: Enforce a consistent naming pattern for the filename of the specified file extension
• check-file/no-index: A file cannot be named "index"