A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/eslint/json below:

eslint/json: JSON language plugin for ESLint

ESLint JSON Language Plugin

This package contains a plugin that allows you to natively lint JSON, JSONC, and JSON5 files using ESLint.

Important: This plugin requires ESLint v9.6.0 or higher and you must be using the new configuration system.

For Node.js and compatible runtimes:

npm install @eslint/json -D
# or
yarn add @eslint/json -D
# or
pnpm install @eslint/json -D
# or
bun add @eslint/json -D

For Deno:

This package exports these languages:

Depending on which types of JSON files you'd like to lint, you can set up your eslint.config.js file to include just the files you'd like. Here's an example that lints JSON, JSONC, and JSON5 files:

// eslint.config.js
import { defineConfig } from "eslint/config";
import json from "@eslint/json";

export default defineConfig([
	{
		plugins: {
			json,
		},
	},

	// lint JSON files
	{
		files: ["**/*.json"],
		language: "json/json",
		rules: {
			"json/no-duplicate-keys": "error",
		},
	},

	// lint JSONC files
	{
		files: ["**/*.jsonc", ".vscode/*.json"],
		language: "json/jsonc",
		rules: {
			"json/no-duplicate-keys": "error",
		},
	},

	// lint JSON5 files
	{
		files: ["**/*.json5"],
		language: "json/json5",
		rules: {
			"json/no-duplicate-keys": "error",
		},
	},
]);

In CommonJS format:

// eslint.config.js
const { defineConfig } = require("eslint/config");
const json = require("@eslint/json").default;

module.exports = defineConfig([
	{
		plugins: {
			json,
		},
	},

	// lint JSON files
	{
		files: ["**/*.json"],
		language: "json/json",
		rules: {
			"json/no-duplicate-keys": "error",
		},
	},

	// lint JSONC files
	{
		files: ["**/*.jsonc", ".vscode/*.json"],
		language: "json/jsonc",
		rules: {
			"json/no-duplicate-keys": "error",
		},
	},

	// lint JSON5 files
	{
		files: ["**/*.json5"],
		language: "json/json5",
		rules: {
			"json/no-duplicate-keys": "error",
		},
	},
]);
Recommended Configuration

To use the recommended configuration for this plugin, specify your matching files and then use the extends: ["json/recommended"] property, like this:

// eslint.config.js
import { defineConfig } from "eslint/config";
import json from "@eslint/json";

export default defineConfig([
	// lint JSON files
	{
		files: ["**/*.json"],
		ignores: ["package-lock.json"],
		plugins: { json },
		language: "json/json",
		extends: ["json/recommended"],
	},

	// lint JSONC files
	{
		files: ["**/*.jsonc"],
		plugins: { json },
		language: "json/jsonc",
		extends: ["json/recommended"],
	},

	// lint JSON5 files
	{
		files: ["**/*.json5"],
		plugins: { json },
		language: "json/json5",
		extends: ["json/recommended"],
	},
]);

Note: You generally want to ignore package-lock.json because it is auto-generated and you typically will not want to manually make changes to it.

In JSONC and JSON5 files, you can also use rule configurations comments and disable directives.

Both line and block comments can be used for all kinds of configuration comments.

Allowing trailing commas in JSONC

The Microsoft implementation of JSONC optionally allows for trailing commas in objects and arrays (files like tsconfig.json have this option enabled by default in Visual Studio Code). To enable trailing commas in JSONC files, use the allowTrailingCommas language option, as in this example:

// eslint.config.js
import { defineConfig } from "eslint/config";
import json from "@eslint/json";

export default defineConfig([
	// lint JSONC files
	{
		files: ["**/*.jsonc"],
		plugins: { json },
		language: "json/jsonc",
		extends: ["json/recommended"],
	},

	// lint JSONC files and allow trailing commas
	{
		files: ["**/tsconfig.json", ".vscode/*.json"],
		plugins: { json },
		language: "json/jsonc",
		languageOptions: {
			allowTrailingCommas: true,
		},
		extends: ["json/recommended"],
	},
]);

Note: The allowTrailingCommas option is only valid for the json/jsonc language.

Frequently Asked Questions How does this relate to eslint-plugin-json and eslint-plugin-jsonc?

This plugin implements JSON parsing for ESLint using the language plugins API, which is the official way of supporting non-JavaScript languages in ESLint. This differs from the other plugins:

As such, this plugin is more robust and faster than the others. You can write your own custom rules when using the languages in this plugin, too.

What about missing rules that are available in eslint-plugin-json and eslint-plugin-jsonc?

Most of the rules in eslint-plugin-json are actually syntax errors that are caught automatically by the parser used in this plugin.

Similarly, many of the rules in eslint-plugin-jsonc specifically disallow valid JavaScript syntax that is invalid in the context of JSON. These are also automatically caught by the parser in this plugin.

Any other rules that catch potential problems in JSON are welcome to be implemented. You can open an issue to propose a new rule.

First, ensure you have the ESLint plugin installed.

Then, edit eslint.validate in your settings.json file to include json, jsonc, and json5:

{
	"eslint.validate": ["json", "jsonc", "json5"]
}

For any JetBrains WebStorm, configure the ESLint scope to include json, jsonc, and json5, such as:

**/*.{js,ts,jsx,tsx,cjs,cts,mjs,mts,html,vue,json,jsonc,json5}

Apache 2.0

The following companies, organizations, and individuals support ESLint's ongoing maintenance and development. Become a Sponsor to get your logo on our READMEs and website.

Technology sponsors allow us to use their products and services for free as part of a contribution to the open source ecosystem and our work.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4