denoland-deno/tests/specs/lint/lint_plugin_utf16/lint.out

error[test-plugin/my-rule]: should be equal to string "1"
 --> [WILDLINE]main.ts:1:15
  | 
1 | const value = "𝄞";
  |               ^^^

  docs: https://docs.deno.com/lint/rules/test-plugin/my-rule


Found 1 problem (1 fixable via --fix)
Checked 2 files
feat(lint): add JavaScript plugin support (#27203) This commit adds an unstable lint plugin API. Plugins are specified in the `deno.json` file under `lint.plugins` option like so: ``` { "lint": { "plugins": [ "./plugins/my-plugin.ts", "jsr:@deno/lint-plugin1", "npm:@deno/lint-plugin2" ] } } ``` The API is considered unstable and might be subject to changes in the future. Plugin API was modelled after ESLint API for the most part, but there are no guarantees for compatibility. The AST format exposed to plugins is closely modelled after the AST that `typescript-eslint` uses. Lint plugins use the visitor pattern and can add diagnostics like so: ``` export default { name: "lint-plugin", rules: { "plugin-rule": { create(context) { return { Identifier(node) { if (node.name === "a") { context.report({ node, message: "should be b", fix(fixer) { return fixer.replaceText(node, "_b"); }, }); } }, }; }, }, }, } satisfies Deno.lint.Plugin; ``` Besides reporting errors (diagnostics) plugins can provide automatic fixes that use text replacement to apply changes. --------- Co-authored-by: Marvin Hagemeister <marvin@deno.com> Co-authored-by: David Sherret <dsherret@gmail.com> 2025-02-05 16:59:24 +01:00			`error[test-plugin/my-rule]: should be equal to string "1"`
			`--> [WILDLINE]main.ts:1:15`
			`\|`
			`1 \| const value = "𝄞";`
			`\| ^^^`

			`docs: https://docs.deno.com/lint/rules/test-plugin/my-rule`


			`Found 1 problem (1 fixable via --fix)`
			`Checked 2 files`