foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-11-24 15:19:26 -05:00
Code Issues Packages 1 Wiki Activity
denoland-deno/.dprint.json

84 lines
2.7 KiB
JSON
Raw Normal View History

Use dprint for internal formatting (#6682)
2020-07-14 15:24:17 -04:00
{
"typescript": {
"deno": true
},
"markdown": {
fix(fmt): Correctly format hard breaks in markdown (#9742)
2021-03-10 08:17:24 -05:00
"deno": true
},
"json": {
"deno": true
Use dprint for internal formatting (#6682)
2020-07-14 15:24:17 -04:00
},
chore: format yaml internally (#24520) Uses https://github.com/g-plane/pretty_yaml
2024-07-10 23:59:57 -04:00
"yaml": {
"quotes": "preferSingle"
},
chore: use `rustfmt` cli via dprint for faster format (#13735)
2022-02-21 12:47:08 -05:00
"exec": {
chore: upgrade to dprint 0.40 internally (#19998)
2023-07-31 11:10:10 -04:00
"commands": [{
"command": "rustfmt --config imports_granularity=item",
"exts": ["rs"]
}]
chore: use `rustfmt` cli via dprint for faster format (#13735)
2022-02-21 12:47:08 -05:00
},
Use dprint for internal formatting (#6682)
2020-07-14 15:24:17 -04:00
"excludes": [
".cargo_home",
chore: reference dprint config file in format script (#8318) * chore: reference dprint config file in format script * chore: ignore .git folder in dprint config
2020-11-09 14:56:43 -05:00
".git",
Add LSP benchmark mimicking the one on quick-lint-js (#13365)
2022-01-18 06:58:50 -05:00
"cli/bench/testdata/express-router.js",
chore(lsp): Add benchmark for performance on a large real-world repo (#23395) This PR adds a benchmark intended to measure how the LSP handles larger repos, as well as its performance on a more realistic workload. The repo being benchmarked is [deco-cx/apps](https://github.com/deco-cx/apps) which has been vendored along with its dependencies. It's included as a git submodule as its fairly large. The LSP requests used in the benchmark are the actual requests sent by VSCode as I opened, modified, and navigated around a file (to simulate an actual user interaction). The main motivation is to have a more realistic benchmark that measures how we do with a large number of files and dependencies. The improvements made from 1.42 to 1.42.3 mostly improved performance with larger repos, so none of our existing benchmarks showed an improvement. Here are the results for the changes made from 1.42 to 1.42.3 (the new benchmark is the last one listed): **1.42.0** ```test Starting Deno benchmark -> Start benchmarking lsp - Simple Startup/Shutdown (10 runs, mean: 379ms) - Big Document/Several Edits (5 runs, mean: 1142ms) - Find/Replace (10 runs, mean: 51ms) - Code Lens (10 runs, mean: 443ms) - deco-cx/apps Multiple Edits + Navigation (5 runs, mean: 25121ms) <- End benchmarking lsp ``` **1.42.3** ```text Starting Deno benchmark -> Start benchmarking lsp - Simple Startup/Shutdown (10 runs, mean: 383ms) - Big Document/Several Edits (5 runs, mean: 1135ms) - Find/Replace (10 runs, mean: 55ms) - Code Lens (10 runs, mean: 440ms) - deco-cx/apps Multiple Edits + Navigation (5 runs, mean: 11675ms) <- End benchmarking lsp ```
2024-04-16 15:26:51 -04:00
"cli/bench/testdata/lsp_benchdata/",
feat: npm workspace and better Deno workspace support (#24334) Adds much better support for the unstable Deno workspaces as well as support for npm workspaces. npm workspaces is still lacking in that we only install packages into the root node_modules folder. We'll make it smarter over time in order for it to figure out when to add node_modules folders within packages. This includes a breaking change in config file resolution where we stop searching for config files on the first found package.json unless it's in a workspace. For the previous behaviour, the root deno.json needs to be updated to be a workspace by adding `"workspace": ["./path-to-pkg-json-folder-goes-here"]`. See details in https://github.com/denoland/deno_config/pull/66 Closes #24340 Closes #24159 Closes #24161 Closes #22020 Closes #18546 Closes #16106 Closes #24160
2024-07-03 20:54:33 -04:00
"cli/bench/testdata/npm/",
"cli/tsc/*typescript.js",
chore: update formatting configuration (#18331)
2023-03-21 17:01:53 -04:00
"cli/tsc/dts/lib.d.ts",
"cli/tsc/dts/lib.decorators*.d.ts",
"cli/tsc/dts/lib.dom*.d.ts",
"cli/tsc/dts/lib.es*.d.ts",
feat: npm workspace and better Deno workspace support (#24334) Adds much better support for the unstable Deno workspaces as well as support for npm workspaces. npm workspaces is still lacking in that we only install packages into the root node_modules folder. We'll make it smarter over time in order for it to figure out when to add node_modules folders within packages. This includes a breaking change in config file resolution where we stop searching for config files on the first found package.json unless it's in a workspace. For the previous behaviour, the root deno.json needs to be updated to be a workspace by adding `"workspace": ["./path-to-pkg-json-folder-goes-here"]`. See details in https://github.com/denoland/deno_config/pull/66 Closes #24340 Closes #24159 Closes #24161 Closes #22020 Closes #18546 Closes #16106 Closes #24160
2024-07-03 20:54:33 -04:00
"cli/tsc/dts/lib.scripthost.d.ts",
"cli/tsc/dts/lib.webworker*.d.ts",
chore: update formatting configuration (#18331)
2023-03-21 17:01:53 -04:00
"cli/tsc/dts/typescript.d.ts",
feat: npm workspace and better Deno workspace support (#24334) Adds much better support for the unstable Deno workspaces as well as support for npm workspaces. npm workspaces is still lacking in that we only install packages into the root node_modules folder. We'll make it smarter over time in order for it to figure out when to add node_modules folders within packages. This includes a breaking change in config file resolution where we stop searching for config files on the first found package.json unless it's in a workspace. For the previous behaviour, the root deno.json needs to be updated to be a workspace by adding `"workspace": ["./path-to-pkg-json-folder-goes-here"]`. See details in https://github.com/denoland/deno_config/pull/66 Closes #24340 Closes #24159 Closes #24161 Closes #22020 Closes #18546 Closes #16106 Closes #24160
2024-07-03 20:54:33 -04:00
"ext/websocket/autobahn/reports",
"gh-pages",
"target",
"tests/ffi/tests/test.js",
"tests/node_compat/runner/suite",
"tests/node_compat/runner/TODO.md",
chore(tests): Remove vestiges of cli/tests folder (#22712)
2024-03-05 15:49:21 -05:00
"tests/node_compat/test",
chore(test): move npm registries to separate servers and to the `tests/registry` folder (#23717) 1. Moves the npm registries to their own dedicated ports. 2. Moves the data files out of `tests/testdata/npm/registry` to `tests/registry/npm`.
2024-05-06 21:06:01 -04:00
"tests/registry/",
feat: default to TS for file extension and support ext flag in more scenarios (#25472) Closes #11220 Currently does lint, fmt, and repl
2024-09-18 15:15:13 -04:00
"tests/specs/bench/default_ts",
feat: npm workspace and better Deno workspace support (#24334) Adds much better support for the unstable Deno workspaces as well as support for npm workspaces. npm workspaces is still lacking in that we only install packages into the root node_modules folder. We'll make it smarter over time in order for it to figure out when to add node_modules folders within packages. This includes a breaking change in config file resolution where we stop searching for config files on the first found package.json unless it's in a workspace. For the previous behaviour, the root deno.json needs to be updated to be a workspace by adding `"workspace": ["./path-to-pkg-json-folder-goes-here"]`. See details in https://github.com/denoland/deno_config/pull/66 Closes #24340 Closes #24159 Closes #24161 Closes #22020 Closes #18546 Closes #16106 Closes #24160
2024-07-03 20:54:33 -04:00
"tests/specs/fmt",
"tests/specs/lint/bom",
feat: default to TS for file extension and support ext flag in more scenarios (#25472) Closes #11220 Currently does lint, fmt, and repl
2024-09-18 15:15:13 -04:00
"tests/specs/lint/default_ts",
add tests
2024-11-06 18:47:21 -05:00
"tests/specs/lint/minified",
fix: enable the reporting of parsing related problems when running deno lint (#24332)
2024-07-23 17:17:17 -04:00
"tests/specs/lint/syntax_error_reporting",
fix(publish): surface syntax errors when using --no-check (#24620)
2024-07-17 23:06:30 -04:00
"tests/specs/publish/no_check_surfaces_syntax_error",
feat: default to TS for file extension and support ext flag in more scenarios (#25472) Closes #11220 Currently does lint, fmt, and repl
2024-09-18 15:15:13 -04:00
"tests/specs/run/default_ts",
"tests/specs/test/default_ts",
chore: move cli/tests/ -> tests/ (#22369) This looks like a massive PR, but it's only a move from cli/tests -> tests, and updates of relative paths for files. This is the first step towards aggregate all of the integration test files under tests/, which will lead to a set of integration tests that can run without the CLI binary being built. While we could leave these tests under `cli`, it would require us to keep a more complex directory structure for the various test runners. In addition, we have a lot of complexity to ignore various test files in the `cli` project itself (cargo publish exclusion rules, autotests = false, etc). And finally, the `tests/` folder will eventually house the `test_ffi`, `test_napi` and other testing code, reducing the size of the root repo directory. For easier review, the extremely large and noisy "move" is in the first commit (with no changes -- just a move), while the remainder of the changes to actual files is in the second commit.
2024-02-10 15:22:13 -05:00
"tests/testdata/byte_order_mark.ts",
"tests/testdata/encoding",
feat: npm workspace and better Deno workspace support (#24334) Adds much better support for the unstable Deno workspaces as well as support for npm workspaces. npm workspaces is still lacking in that we only install packages into the root node_modules folder. We'll make it smarter over time in order for it to figure out when to add node_modules folders within packages. This includes a breaking change in config file resolution where we stop searching for config files on the first found package.json unless it's in a workspace. For the previous behaviour, the root deno.json needs to be updated to be a workspace by adding `"workspace": ["./path-to-pkg-json-folder-goes-here"]`. See details in https://github.com/denoland/deno_config/pull/66 Closes #24340 Closes #24159 Closes #24161 Closes #22020 Closes #18546 Closes #16106 Closes #24160
2024-07-03 20:54:33 -04:00
"tests/testdata/file_extensions/ts_with_js_extension.js",
chore: move cli/tests/ -> tests/ (#22369) This looks like a massive PR, but it's only a move from cli/tests -> tests, and updates of relative paths for files. This is the first step towards aggregate all of the integration test files under tests/, which will lead to a set of integration tests that can run without the CLI binary being built. While we could leave these tests under `cli`, it would require us to keep a more complex directory structure for the various test runners. In addition, we have a lot of complexity to ignore various test files in the `cli` project itself (cargo publish exclusion rules, autotests = false, etc). And finally, the `tests/` folder will eventually house the `test_ffi`, `test_napi` and other testing code, reducing the size of the root repo directory. For easier review, the extremely large and noisy "move" is in the first commit (with no changes -- just a move), while the remainder of the changes to actual files is in the second commit.
2024-02-10 15:22:13 -05:00
"tests/testdata/fmt/",
feat: npm workspace and better Deno workspace support (#24334) Adds much better support for the unstable Deno workspaces as well as support for npm workspaces. npm workspaces is still lacking in that we only install packages into the root node_modules folder. We'll make it smarter over time in order for it to figure out when to add node_modules folders within packages. This includes a breaking change in config file resolution where we stop searching for config files on the first found package.json unless it's in a workspace. For the previous behaviour, the root deno.json needs to be updated to be a workspace by adding `"workspace": ["./path-to-pkg-json-folder-goes-here"]`. See details in https://github.com/denoland/deno_config/pull/66 Closes #24340 Closes #24159 Closes #24161 Closes #22020 Closes #18546 Closes #16106 Closes #24160
2024-07-03 20:54:33 -04:00
"tests/testdata/fmt/badly_formatted.ipynb",
"tests/testdata/fmt/badly_formatted.json",
"tests/testdata/fmt/badly_formatted.md",
chore: move cli/tests/ -> tests/ (#22369) This looks like a massive PR, but it's only a move from cli/tests -> tests, and updates of relative paths for files. This is the first step towards aggregate all of the integration test files under tests/, which will lead to a set of integration tests that can run without the CLI binary being built. While we could leave these tests under `cli`, it would require us to keep a more complex directory structure for the various test runners. In addition, we have a lot of complexity to ignore various test files in the `cli` project itself (cargo publish exclusion rules, autotests = false, etc). And finally, the `tests/` folder will eventually house the `test_ffi`, `test_napi` and other testing code, reducing the size of the root repo directory. For easier review, the extremely large and noisy "move" is in the first commit (with no changes -- just a move), while the remainder of the changes to actual files is in the second commit.
2024-02-10 15:22:13 -05:00
"tests/testdata/import_attributes/json_with_shebang.json",
feat: npm workspace and better Deno workspace support (#24334) Adds much better support for the unstable Deno workspaces as well as support for npm workspaces. npm workspaces is still lacking in that we only install packages into the root node_modules folder. We'll make it smarter over time in order for it to figure out when to add node_modules folders within packages. This includes a breaking change in config file resolution where we stop searching for config files on the first found package.json unless it's in a workspace. For the previous behaviour, the root deno.json needs to be updated to be a workspace by adding `"workspace": ["./path-to-pkg-json-folder-goes-here"]`. See details in https://github.com/denoland/deno_config/pull/66 Closes #24340 Closes #24159 Closes #24161 Closes #22020 Closes #18546 Closes #16106 Closes #24160
2024-07-03 20:54:33 -04:00
"tests/testdata/lint/glob/",
"tests/testdata/malformed_config/",
"tests/testdata/run/byte_order_mark.ts",
chore: move cli/tests/ -> tests/ (#22369) This looks like a massive PR, but it's only a move from cli/tests -> tests, and updates of relative paths for files. This is the first step towards aggregate all of the integration test files under tests/, which will lead to a set of integration tests that can run without the CLI binary being built. While we could leave these tests under `cli`, it would require us to keep a more complex directory structure for the various test runners. In addition, we have a lot of complexity to ignore various test files in the `cli` project itself (cargo publish exclusion rules, autotests = false, etc). And finally, the `tests/` folder will eventually house the `test_ffi`, `test_napi` and other testing code, reducing the size of the root repo directory. For easier review, the extremely large and noisy "move" is in the first commit (with no changes -- just a move), while the remainder of the changes to actual files is in the second commit.
2024-02-10 15:22:13 -05:00
"tests/testdata/run/error_syntax_empty_trailing_line.mjs",
"tests/testdata/run/inline_js_source_map*",
"tests/testdata/test/markdown_windows.md",
chore: move `test_util/std` to `tests/util/std` (#22402) Note: tests are not the only part of the codebase that uses `std`. Other parts, like `tools/`, do too. So, it could be argued that this is a little misleading. Either way, I'm doing this as discussed with @mmastrac.
2024-02-13 11:22:49 -05:00
"tests/util/std",
chore: move `tools/wpt` to `tests/wpt/runner` (#22545) Towards #22525 --------- Signed-off-by: Asher Gomez <ashersaupingomez@gmail.com> Co-authored-by: Matt Mastracci <matthew@mastracci.com>
2024-03-04 19:41:16 -05:00
"tests/wpt/runner/expectation.json",
"tests/wpt/runner/manifest.json",
feat: npm workspace and better Deno workspace support (#24334) Adds much better support for the unstable Deno workspaces as well as support for npm workspaces. npm workspaces is still lacking in that we only install packages into the root node_modules folder. We'll make it smarter over time in order for it to figure out when to add node_modules folders within packages. This includes a breaking change in config file resolution where we stop searching for config files on the first found package.json unless it's in a workspace. For the previous behaviour, the root deno.json needs to be updated to be a workspace by adding `"workspace": ["./path-to-pkg-json-folder-goes-here"]`. See details in https://github.com/denoland/deno_config/pull/66 Closes #24340 Closes #24159 Closes #24161 Closes #22020 Closes #18546 Closes #16106 Closes #24160
2024-07-03 20:54:33 -04:00
"tests/wpt/suite",
chore: deprecate run itests (#26444)
2024-11-05 01:39:05 -05:00
"third_party",
"tests/specs/run/shebang_with_json_imports_tsc",
"tests/specs/run/shebang_with_json_imports_swc",
"tests/specs/run/ext_flag_takes_precedence_over_extension",
"tests/specs/run/error_syntax_empty_trailing_line/error_syntax_empty_trailing_line.mjs"
Use dprint for internal formatting (#6682)
2020-07-14 15:24:17 -04:00
],
"plugins": [
fix(fmt): do not panic for jsx ignore container followed by jsx text (#26723)
2024-11-04 15:40:05 -05:00
"https://plugins.dprint.dev/typescript-0.93.2.wasm",
fix(install): better json editing (#26450) 1. Respects the formatting of the file (ex. keeps four space indents or tabs). 2. Handles editing of comments. 3. Handles trailing commas. 4. Code is easier to maintain.
2024-10-21 14:17:08 -04:00
"https://plugins.dprint.dev/json-0.19.4.wasm",
fix(fmt/markdown): fix regression with multi-line footnotes and inline math (#25222) What happened in this specific case was the parser used to actually treat these as code block. Now it treats it as a multi-paragraph footnote and that caused the issue - https://github.com/dprint/dprint-plugin-markdown/pull/121/files
2024-08-26 14:36:24 -04:00
"https://plugins.dprint.dev/markdown-0.17.8.wasm",
refactor: move ByonmNpmResolver to deno_resolver (#25937) Some more slow progress on moving all the resolution code into deno_resolver.
2024-09-30 09:33:32 -04:00
"https://plugins.dprint.dev/toml-0.6.3.wasm",
fix(fmt): was sometimes putting comments in front of commas in parameter lists (#24650) * https://github.com/dprint/dprint-plugin-typescript/pull/651
2024-07-19 11:58:21 -04:00
"https://plugins.dprint.dev/exec-0.5.0.json@8d9972eee71fa1590e04873540421f3eda7674d0f1aae3d7c788615e7b7413d0",
fix(fmt/markdown): fix regression with multi-line footnotes and inline math (#25222) What happened in this specific case was the parser used to actually treat these as code block. Now it treats it as a multi-paragraph footnote and that caused the issue - https://github.com/dprint/dprint-plugin-markdown/pull/121/files
2024-08-26 14:36:24 -04:00
"https://plugins.dprint.dev/g-plane/pretty_yaml-v0.5.0.wasm"
Use dprint for internal formatting (#6682)
2020-07-14 15:24:17 -04:00
]
}
Copy permalink