foster/deno
0
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2025-03-05 18:37:20 -05:00
Code Issues Packages 1 Wiki Activity
deno/tests/specs/lint/lint_plugin/__test__.jsonc

19 lines
302 B
JSON
Raw Normal View History

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
{
perf(lsp): add built-in tracing support for the LSP (#27843) adds tracing and opentelemetry exporting to the LSP. enable it in `.vscode/settings.json` (or wherever you configure the LSP), like ``` { "deno.tracing": true } ``` which will by default export opentelemetry traces to `localhost:4317` or ``` { "deno.tracing": { // all fields optional "collector": "openTelemetry" (default) | "logging" (output in lsp log window) "collectorEndpoint": "http://localhost:4318" (for opentelemetry) "enable": true | false, "filter": "info" // defaults to "info", but can be any span filter } } ``` --- a full working setup would be 1: Run jaeger (an opentelemetry collector with a nice UI): ``` docker run --rm -p 16686:16686 -p 4317:4317 jaegertracing/jaeger ``` 2. Enable in .vscode/settings.json ``` { "deno.tracing": true } ``` 3. Restart LSP (right now it only will start the opentelemetry exporter on LSP startup) 3. open `http://localhost:16686` in your browser --------- Co-authored-by: Nathan Whitaker <nathan@deno.com>
2025-02-12 17:40:40 +01:00
"tempDir": true,
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
"steps": [
{
"args": "lint a.ts",
"output": "lint.out",
"exitCode": 1
},
{
"args": "lint -c deno_exclude.json a.ts",
"output": "lint_exclude.out"
},
{
"args": "lint --fix a.ts",
"output": "lint_fixed.out"
}
]
}
Copy permalink