deno.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2024-02-14	feat(lsp): jsr support with cache probing (#22418)	Nayeem Rahman

2024-02-14	feat(publish): allow passing config flag (#22416)	Leo Kettmeir

2024-02-12	chore: continue tests/ re-org (#22396)	Matt Mastracci
	Split `node_compat_tests` into its own top-level test so its stdout doesn't stomp on the remainder of the tests.
2024-02-12	feat(lsp): jsr support first pass (#22382)	Nayeem Rahman
	This implementation heavily depends on there being a lockfile, meaning JSR specifiers will always diagnose as uncached unless it's there. In practice this affects cases where a `deno.json` isn't being used. Our NPM specifier support isn't subject to this. The reason for this is that the version constraint solving code is currently buried in `deno_graph` and not usable from the LSP, so the only way to reuse that logic is the solved-version map in the lockfile's `packages.specifiers`.
2024-02-12	chore: move test_ffi and test_nap to tests/ [WIP] (#22394)	Matt Mastracci
	Moving some additional NAPI and. FFI tests out of the tree root.
2024-02-12	fix(console): support NO_COLOR and colors option in all scenarios (#21910)	Leo Kettmeir
	Noticed in #21607
2024-02-10	chore: move cli/tests/ -> tests/ (#22369)	Matt Mastracci
	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.