7531 commits

Author	SHA1	Message	Date
Nathan Whitaker	c36a20f6bb	feat(run): resolve main module with workspace resolver (#29928) ... Closes https://github.com/denoland/deno/issues/29897. Closes https://github.com/denoland/deno/issues/14066. Closes https://github.com/denoland/deno/issues/19955. With this PR we'll attempt to resolve bare specifiers passed to `run` or `serve` with the workspace resolver. This means you can run specifiers that are defined in your import map/package.json. If the specifier looks like a path (starts with `.`, or is an absolute path) then we won't try to resolve it via the import map. This does have the potential to break someone, in the case that you have something like ``` { "imports": { "foo.ts": "./bar.ts" } } ``` and you have a file named `foo.ts`, previously `deno run foo.ts` would run `./foo.ts`, now we would run `./bar.ts`. I can't see a way around that without doing an extra stat to see if the file exists, or deferring this to module load time (which seems complex). I don't think many people would hit that, and if someone does there's a simple fix – just add `./` to the front. From my benchmarking, this change has no effect on startup time	2025-06-27 19:14:30 -07:00
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
Simon Lecoq	7554b28a04	fix: support Deno.permissions.query({name:"import"}) (#29610) ... Closes #27050	2025-06-26 22:13:56 +02:00
David Emanuel Buchmann	3cefece2da	feat: --allow-net supports CIDR ranges (#29704) ... This commit adds support for specifying CIDR ranges in `--allow-net` and `--deny-net` flag: Eg: trying to run `deno run --allow-net --deny-net=192.168.0.0/16` and `fetch` from `http://127.0.0.1:4545/` will raise `NotCapable` error.	2025-06-26 22:13: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	2ed8a1d675	chore: add back node-globals to json schema (#29899)	2025-06-26 17:11:18 +00:00
Nayeem Rahman	99ae41f6bb	feat: stabilize --allow-net subdomain wildcards (#29902) ... Closes #29499.	2025-06-26 17:00:43 +00:00
David Sherret	ec32c6e5ba	feat(unstable): bytes and text imports (#29855)	2025-06-26 11:21:16 -04:00
Nayeem Rahman	880ed76b99	fix(lsp): don't show no-export diagnostics for type-only npm imports (#29888)	2025-06-26 15:53:05 +01: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
Daniel Osvaldo R	9bcd4366ee	fix(ext/node): add lchmod, lchmod promise, lchmodSync to node:fs (#29833)	2025-06-26 15:46:07 +09:00
David Sherret	4a0cd18a6b	fix(install/global): resolve bin name from npm packument (#29884)	2025-06-25 15:10:26 -04:00
Bartek Iwańczuk	f781796402	feat: Deno.execPath() no longer requires --allow-read permission (#29620) ... This commit changes `Deno.execPath()` API to no longer require read permission. This change is dictated by the fact that in common scenarios, requiring read permission is less secure than not requiring permissions - if a user wants to spawn a Deno subprocess using the current executable, they would do something like: ``` new Deno.Command(Deno.execPath(), { args: ["eval", "1+1"] }).outputSync(); ``` To run this program, currently one needs to pass `--allow-read --allow-run=deno` flags. It's possible to limit scope of `--allow-read` flag, but it's really cumbersome to do, so most users will opt to give a blanket `--allow-read` permission. Not requiring read permissions allows the above program to be run with just `--allow-run=deno` flag. This change is in similar to relaxing of permissions in `Deno.cwd()` API done in https://github.com/denoland/deno/pull/27192. Ref https://github.com/denoland/deno/issues/20061#issuecomment-2942497783	2025-06-25 20:57:35 +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	695df57358	fix(fmt/css): prefer collapsing font-family values (#29864) ... Closes https://github.com/denoland/deno/issues/29336	2025-06-24 20:28:53 +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
Leo Kettmeir	38f6720185	feat: unflag the deploy subcommand (#29863)	2025-06-24 12:23:58 +00:00
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
denobot	0d76cd50af	2.3.7 (#29853) ... Bumped versions for 2.3.7 --------- Co-authored-by: bartlomieju <bartlomieju@users.noreply.github.com> Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>	2025-06-23 23:51:36 +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
David Sherret	2205ca5e4a	chore: reduce some allocations collecting unstable features (#29827) ... Minor thing.	2025-06-20 16:24:57 +00:00
snek	e99b1c1f86	feat: allow base64 ca cert in args (#29814) ... This allows loading a base64 encoded cert directly from arg/env by prefixing it with `base64:`	2025-06-19 11:04:16 +00:00
Divy Srivastava	d84866e933	chore: use aws_lc_rs (#28244)	2025-06-19 01:07:00 -07:00
Nathan Whitaker	b383433708	fix(install): ignore unknown JSR export errors on top level install (#29807) ... Couldn't write a test, but it happens in some edge cases.	2025-06-18 18:37:14 +00:00
David Sherret	400a9565c3	chore: move unsafe_use_unprotected_platform feature to cli dev dep (#29806) ... The tests crate doesn't have a dependency on deno_core. Amendment to https://github.com/denoland/deno/pull/29794	2025-06-18 14:16:09 -04: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
Bartek Iwańczuk	27ea4ef930	refactor(bundle): split up into several helper functions (#29771)	2025-06-16 18:12:47 -07:00
Nayeem Rahman	470aa51886	refactor: rename ts_config to compiler_options (#29769)	2025-06-17 02:07:43 +01: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
Jo Franchetti	2ac14604bc	docs: updating jsdocs for window (#29598) ... Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>	2025-06-16 15:38:17 +00: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	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
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
Nayeem Rahman	8c3e6a14a1	fix(lsp): respect media type for tsx jupyter cells (#29712)	2025-06-12 22:39:59 +01:00