849 commits

Author	SHA1	Message	Date
Nayeem Rahman	8019d9db95	fix(check): don't detect tsconfigs with no deno.json/package.json or --no-config (#29925)	2025-06-27 22:09:55 +00:00
Nathan Whitaker	de02d99a17	feat(bundle): support text and bytes imports in bundle (#29908)	2025-06-26 22:39:58 +00:00
Nayeem Rahman	7a9ab843bd	feat(check): tsconfig "references", "extends", "files", "include" and "exclude" (#29843) ... - Each workspace directory is probed for a `tsconfig.json`. - These and any that are included by their `references` are put into a list ordered by priority. - A tsconfig has lower priority than its `references`. - An earlier listed entry in `references` has higher priority than a later one. - A probed tsconfig in an inner directory has higher priority than an outer one. Their `references` would be interspersed between them. - Each tsconfig has a filter based on its `files`, `include` and `exclude` fields. If it doesn't have `files` or `include`, it will match any path in its containing directory not exempted by `exclude`. - For type-checking, each root path will be allocated compiler options based on the first tsconfig it whose filter it matches from this list. - Only if it doesn't match any tsconfig, it will fall back to using the nearest `deno.json`. If it's a workspace member and the root `deno.json` has `compilerOptions`, these will be merged using the same logic from `extends`. Inheritance between configs strictly occurs via `extends` in a `tsconfig.json`, and between workspace member and root `deno.json`s' `compilerOptions`. There is no implicit inheritance between `tsconfig.json` and `deno.json`. The default compiler options currently applied against tsconfigs are Deno's normal defaults, with the exception of `lib`. The default value for `lib` is `["deno.window", "deno.unstable", "dom"]` for files in the scope of a tsconfig with `lib` unspecified. This behaviour is depended on by, for example, the template project created by `create-vite -> svelte`. I expect we'll add more such exceptions over time with other fields.	2025-06-26 21:17:07 +00:00
Bartek Iwańczuk	9913311860	feat: stabilize --node-conditions flag (#29628) ... Stabilizes `--conditions` flag added in https://github.com/denoland/deno/pull/29586. Closes https://github.com/denoland/deno/issues/23757	2025-06-26 22:52:04 +02:00
Nathan Whitaker	8cefe97b09	fix(bundle): only replace require shim in js files, spruce up output (#29892) ... We were trying to do the hack of replacing the esbuild require shim on every output file, regardless of whether it was js/ts. This fixes that. In addition, this spruces up the output of deno bundle a bit. before:  after: 	2025-06-26 18:35:19 +00:00
Bartek Iwańczuk	0a4f946fd9	feat: add 'deno update' subcommand (#29187) ... Just to save a few characters, because it's an alias to "deno outdated --update" Ref https://github.com/denoland/deno/issues/29778	2025-06-26 19:13:29 +02:00
David Sherret	ec32c6e5ba	feat(unstable): bytes and text imports (#29855)	2025-06-26 11:21:16 -04:00
Bartek Iwańczuk	e8d9d59b83	feat: deprecate --unstable-node-globals flag (#29887) ... `--unstable-node-globals` flag is no longer needed after following PRs had landed: - https://github.com/denoland/deno/pull/29877 - https://github.com/denoland/deno/pull/29734 - https://github.com/denoland/deno/pull/29416 This commit hides this flag from the `--help=unstable` output, but still keep the flag to not break previously working invocations.	2025-06-26 12:49:24 +02:00
Bartek Iwańczuk	a8f59c1af9	feat: add DENO_COMPAT env var (#29889) ... This commit adds the `DENO_COMPAT` env var, that when specified enables several features: - --unstable-bare-node-builtins - --unstable-detect-cjs - --unstable-sloppy-imports With Deno v2.3.x, it is a common situation where these 3 flags have to specified to run an existing Node.js project, causing a friction that many users experience. The idea is that this env var could be "set and forget" for many people, that should provide better DX for running Node.js projects. It is necessary to note that using this env var _impacts performance_ - especially startup time.	2025-06-26 12:06:24 +02:00
Bartek Iwańczuk	1192bc0040	feat: rename --unstable-node-conditions to --unstable-conditions (#29885) ... The `DENO_NODE_CONDITIONS` env var was renamed to `DENO_CONDITIONS`. Ref https://github.com/denoland/deno/pull/29628 Ref https://github.com/denoland/deno/issues/23757	2025-06-26 12:05:57 +02:00
Bartek Iwańczuk	d4b02455df	feat: make setImmediate and clearImmediate as globals (#29877) ... Follow up to https://github.com/denoland/deno/pull/29323 and https://github.com/denoland/deno/pull/29416. This effort is to reduce a number of different globals available to user code and npm dependencies. Also improves performance when these globals are used. This brings the number of "managed globals" down to 6. Towards https://github.com/denoland/deno/issues/29703	2025-06-25 15:21:10 +02:00
Asher Gomez	002a18cf03	feat(ext/http): support onListen() callback in deno serve (#29449) ... Closes #26070 Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>	2025-06-25 15:20:27 +02:00
Yoshiya Hinosawa	56d7660ee4	feat(cli): add --coverage flag to deno run command (#29329) ... closes #16440 This PR adds `--coverage` flag to `deno run` command. When the flag is specified, it generates the coverage profile in the directory specified (default is `coverage`). The coverage directory can also be specified from the env var `DENO_COVERAGE_DIR`. --------- Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>	2025-06-25 13:34:30 +02:00
Bartek Iwańczuk	bff09506bd	feat(unstable): add DENO_NODE_CONDITIONS env var (#29848) ... Follow up to https://github.com/denoland/deno/pull/29586 that adds a `DENO_NODE_CONDITIONS` env var that allows to specify conditional exports when the user can't control CLI flags passed to the command (eg. on Deploy).	2025-06-25 07:16:11 +00:00
Bartek Iwańczuk	4e23d9b5f0	feat(fmt): add support for .xml, .svg and .mustache files (#29851) ... Formatting `.mustache` files still requires `--unstable-component` flag when running `deno fmt` Closes https://github.com/denoland/deno/issues/20205	2025-06-24 17:16:33 +02:00
Bartek Iwańczuk	14f9d77f3d	feat(otel): stabilize OpenTelemetry support (#29822) ... This commit stabilizes support for OpenTelemetry in Deno, effectively removing the need to use `--unstable-otel` flag or using `{ "unstable": ["otel"] }` option in the config file. Supersedes https://github.com/denoland/deno/pull/29500 Closes https://github.com/denoland/deno/issues/29477	2025-06-24 16:49:04 +02:00
Bartek Iwańczuk	ed0c77edb3	feat: make 'Buffer' and 'global' available as globals (#29416) ... Follow up to https://github.com/denoland/deno/pull/29323. This effort is to reduce a number of different globals available to user code and npm dependencies. Also improves performance when these globals are used. Towards https://github.com/denoland/deno/issues/29703	2025-06-24 14:31:06 +02:00
Bartek Iwańczuk	c50b37c234	test: fix specs::coverage::data_url test (#29865)	2025-06-24 16:22:28 +05:30
Boye Lillejord-Nygård	ef6ff554b0	fix(bench): Make output table markdown compatible (#29532) ... This changes the format of the table outputted by `deno bench` to be markdown compatible. Related #29533 Closes #29466	2025-06-24 11:27:42 +02:00
Boye Lillejord-Nygård	5b65313d48	fix(coverage): Make output table markdown compatible (#29533) ... This changes the format of the table outputted by `deno coverage` to be markdown compatible. Related #29532 Closes #29465	2025-06-24 11:27:07 +02:00
Bartek Iwańczuk	fd352537ce	feat: add DENO_AUTO_SERVE env var (#29852) ... This commits adds `DENO_AUTO_SERVE` env var, that when specified makes `deno run` behave like `deno serve` if the entrypoint satisfies the `Deno.ServeDefaultExport` interface.	2025-06-24 11:05:59 +02:00
Nathan Whitaker	19d08d12d3	fix(bundle): transform import.meta.main (#29830) ... For entrypoints, it remains untouched. For non-entrypoints it becomes `false`.	2025-06-23 20:51:24 +00:00
David Sherret	0f08eb076b	fix(jsr): allow using import.meta.resolve to resolve non-jsr remote urls (#29831) ... This was too restrictive. Closes https://github.com/denoland/deno/issues/25579	2025-06-20 22:05:38 +00:00
Nathan Whitaker	03651c773f	feat(bundle): add watch mode to bundle (#29795) ... Reuses the same esbuild subprocess, and triggers rebuilds on file changes. Esbuild will reuse parsed sources that are unchanged, so subsequent builds are faster than the initial one	2025-06-18 08:35:12 -07:00
Janosh Riebesell	59c416662b	fix(fmt): handle TS as syntax in Svelte each block (#29789) ... Closes #29768	2025-06-17 20:10:06 +02:00
Yoshiya Hinosawa	e5b96243ac	test: fix flakiness of specs::coverage::data_url (#29760)	2025-06-17 10:54:44 +09:00
Yoshiya Hinosawa	f609bbb267	fix(fmt): fix handling of indent inside template language (#29616) ... This commit fixes the handling of indent inside the template languages. See https://github.com/dprint/dprint-plugin-typescript/pull/718 for details	2025-06-17 09:00:18 +09:00
Nathan Whitaker	bf6292b170	fix(bundle): improve error handling and reporting (#29744) ... We were effectively ignoring our diagnostics, and instead falling back to esbuild (and then displaying the esbuild diagnostics). That was mostly for simplicity and so we would fall back to esbuild handling unsupported things (for instance css imports). This does a small refactor on the module loader to give us an API that doesn't have to adhere to the deno_core ModuleLoader API. That lets us return and handle errors more concretely, instead of having indirection and downcasting. Now, we only ignore our errors about being unable to load unsupport file types, and the rest we handle ourselves. I've also aligned the formatting of esbuild errors with ours, so it should be more uniform. A few examples (dbgdeno is just an alias for the debug build of this PR): 	2025-06-16 14:11:14 -07:00
David Sherret	c064b6d594	fix: import.meta.resolve - do not error for non-existent files in npm packages (#29741) ... This further improves `import.meta.resolve` to not error in many more scenarios (better alignment with Node). 1. Non-existent files in npm packages 1. Non-existent built-in node modules (ex. `node:non-existent`) 1. Many things that were previously errors with byonm. 1. No longer surfaces some deno_graph resolution errors Additionally, this defers resolving npm specifiers until loading for dynamic imports in order to have `prepare_load` properly install them loading. Before it could potentially error when loading the same npm specifier on multiple workers (reason for flaky `specs::npm::worker_shutdown_during_npm_import`).	2025-06-16 12:03:12 +02:00
David Sherret	d15a302d41	refactor: add deno_config crate back to cli (#29740) ... Co-authored-by: nayeemrmn <nayeemrmn@users.noreply.github.com>	2025-06-13 17:01:26 +00:00
David Sherret	3d5ff3cf1c	fix(npm): support resolving npm specifiers not in graph with import.meta.resolve for resolved packages (#29732)	2025-06-13 09:23:19 -04:00
Bartek Iwańczuk	1f02d34877	fix: remove self from global middleware (#29734) ... Follow up to https://github.com/denoland/deno/pull/29543 that does the same for `self` global. Unfortunately this omission led to a problem described in https://github.com/denoland/deno/issues/29726 where packages started thinking that they are being run in a web worker context (because they are!) but the expected "self" global is not there.	2025-06-13 12:48:26 +02:00
Nathan Whitaker	f80075c3ff	feat(bundle): add --sourcemap flag (#29735) ... Closes #29649. --------- Co-authored-by: Yoshiya Hinosawa <stibium121@gmail.com>	2025-06-13 02:55:07 +00:00
Nathan Whitaker	12ed9f3649	fix(bundle): parse the allow-import flag, fix example in help text (#29733) ... Closes #29729.	2025-06-12 21:44:26 -04:00
Nathan Whitaker	be2bb7d5fb	feat(bundle): add --platform flag to bundle (#29697) ... Closes #29650. Currently passing `--platform=browser` does two things: - makes us prefer the `"browser"` key in package json over module and main - makes us prefer the `"browser"` export condition but we may add more things in the future	2025-06-12 20:28:54 -04:00
Nathan Whitaker	09f4118529	fix(bundle): enable sloppy imports by default when bundling (#29731) ... It's more permissive, aligns more with typical bundler behavior, and runtime perf is not as much of a concern	2025-06-12 21:43:13 +00:00
Nathan Whitaker	4072c2c627	fix(install,outdated): try to avoid building graph with incorrect exports (#29713) ... Fixes https://github.com/denoland/deno/issues/29707. Not particularly happy with this one, but the only other idea I had was to just ignore errors about non-existent exports when we build the graph for a top level install. That might end up being the best solution. For background, when you do a top level install that includes a jsr dependency, we fetch the exports for the jsr package and then use those exports as roots in the module graph (which triggers caching those files). To find those exports correctly, we need to know what version will end up being cached, otherwise we may end up trying to reference exports that don't exist on the actual package. Previously, we could just look up the version in the lockfile and that worked, but it turns out that was depending on the behavior that was reverted in https://github.com/denoland/deno/pull/29642.	2025-06-12 09:23:05 -07:00
Nathan Whitaker	9602e13d53	fix(process,node): roll our own process spawning on windows (#29609) ... Fixes #16899. Fixes https://github.com/denoland/deno/issues/23524. Fixes https://github.com/denoland/deno/issues/23938. Fixes https://github.com/denoland/deno/issues/27869. Unblocks #5501. This PR adds support for additional stdio pipes to windows, as well as the detached option in `node:child_process`. I also ported over the `kill` implementation for windows, which means we now can support `kill(0)` as well as some other signals. This means that playwright will now work on windows. Now that we have a way to support detached processes on all platforms, we can also easily add a `detached` option to `Deno.Command`, similar to `child_process.spawn`. --- The reason for moving away from `std::process::Command` is that the standard library doesn't expose what we need to control the file descriptor table of child processes on windows. The implementation here is based off of parts of `std` and parts of `libuv`, and allows us to support passing extra pipes in addition to detached processes on windows.	2025-06-12 02:56:13 +00:00
Yoshiya Hinosawa	76c95b9c44	fix(fmt): fix line number in error message when syntax error thrown from external formatter (#29698) ... The line number in error message is off by one when external formatter raised syntax error. This commit fixes it by upgrading `dprint-plugin-typescript` (The issue was fixed in upstream https://github.com/dprint/dprint-plugin-typescript/pull/722 )	2025-06-12 08:58:44 +09:00
Bartek Iwańczuk	1a8e5edd0f	fix: remove WorkerGlobalScope from global middleware (#29543) ... This commit removes "WorkerGlobalScope" global from the "global middleware" that we use to provide different set of globals to user code and npm packages. This is done, by renaming "WebWorkerType" to "WorkerThreadType" and introducing a "Node" variant - this variant is used when creating a worker using "node:worker_threads" module. This worker does not have a "WorkerGlobalScope" (because it's not a Web Worker) and the regular Web Worker created using "new Worker" does have it.	2025-06-11 17:19:15 +02:00
David Sherret	56ce3352d2	fix(unstable): rename "patch" property to "links" (#29677) ... This is to help make this feature less ambiguous with `npm patch`, which it's not like. Note: the "patch" property will continue to work for the time being, but the lockfile will have a bit of churn for this unstable property. We're going to merge this in a patch because this feature is unstable.	2025-06-10 21:51:23 +00:00
Nathan Whitaker	4438f8762f	fix(bundle): rework how patterns for externals are handled (#29680) ... Now aligns with esbuild's behavior	2025-06-10 16:58:55 +00:00
Nathan Whitaker	1f579ba89e	fix(bundle): pass requested module type to load (#29683) ... Fixes #29663.	2025-06-10 15:44:32 +00:00
Yoshiya Hinosawa	cb810ab664	fix(fmt): allow omission of semicolon in certain cases in css template (#29687)	2025-06-10 23:19:40 +09:00
Bartek Iwańczuk	ccc30edcb5	fix(ext/node): make conditional exports work in require() (#29640) ... This commit fixes passing conditional exports specified with `--unstable-node-conditions` flag to `require()` calls. Fixes scenario from https://github.com/denoland/deno/issues/23757#issuecomment-2949344042 --------- Co-authored-by: Nayeem Rahman <nayeemrmn99@gmail.com>	2025-06-10 02:09:46 +02:00
David Sherret	d5f0dd7ca2	fix(install): bust packument cache on version not found when loading extra info from lockfile (#29679) ... Co-authored-by: nathanwhit <nathanwhit@users.noreply.github.com>	2025-06-09 23:22:12 +00:00
Nathan Whitaker	64a95cb5fb	fix(bundle): fix handling of multiple entrypoints (#29651) ... Fixes #29648.	2025-06-09 20:15:13 +00:00
Nathan Whitaker	7a837f9fdb	feat(bundle, unstable): bundling backed by esbuild (#29470) ... todo: - [ ] cleanup cli, decide what flags we want to commit to - [x] decide what to do about node addons - (you can mark them external via `--external`) - [x] move `esbuild_rs` to the `denoland` org - [x] figure out the dynamic require issue - [x] figure out how to test this - [x] clean up / revert all the random changes	2025-06-07 21:20:10 +02:00
David Sherret	fb0241388e	fix(install): clean-up lock poll file for a more deterministic node_modules folder output (#29623) ... Closes https://github.com/denoland/deno/issues/29619	2025-06-06 12:58:10 -04:00
Bartek Iwańczuk	ea4506c657	feat(unstable): add --unstable-node-conditions flag for node resolution (#29586) ... This commit adds support for `--unstable-node-conditions` flag that allows to customize "conditional exports" used by Deno. See https://nodejs.org/api/packages.html#resolving-user-conditions for more details. Ref https://github.com/denoland/deno/issues/23757 --------- Co-authored-by: Nayeem Rahman <nayeemrmn99@gmail.com>	2025-06-05 12:32:24 +02:00