1421 commits

Author	SHA1	Message	Date
David Sherret	7b154300b8	refactor: upgrade to deno_core 0.353.0 (#30164)	2025-07-22 10:38:38 -04:00
David Sherret	61a7913a8b	fix(task): show package name of task when --recursive (#30136)	2025-07-17 21:42:50 +00:00
David Sherret	b7680dde5e	fix(task): --recursive - order tasks by package dependencies (#30129) ... Closes https://github.com/denoland/deno/issues/29377	2025-07-17 09:31:58 -04:00
David Sherret	874cb8e1ae	refactor(bundle): remove usage of cli module loader (#30086)	2025-07-15 14:06:42 +00:00
David Sherret	2dd8e085e2	fix(lint): do not panic for many overlapping lint fixes (#30104)	2025-07-14 14:16:44 -04:00
David Sherret	489d9bbdcf	refactor(loader): extract out more module loading code from cli crate (#30084)	2025-07-14 11:27:51 -04:00
David Sherret	1dd0db2e16	refactor(node_resolver): switch to use bundle_mode (#30083) ... Removes `NodeResolutionKind::Bundling` and prefers checking `bundle_mode` instead.	2025-07-11 18:29:15 +00:00
Nayeem Rahman	c65a48a488	fix(lsp): tsconfig features for 'deno check' parity (#30007)	2025-07-08 23:22:13 +01:00
Leo Kettmeir	b59576cc0f	feat(unstable): tunnelling (#30022) ... Co-authored-by: snek <snek@deno.com>	2025-07-08 02:44:50 +02:00
Nathan Whitaker	9d88fb74d6	fix(bundle): don't use createRequire when targeting browser, make hack not depend on variable names (#30023) ... Fixes https://github.com/denoland/deno/issues/29998. Also fixes an issue reported on discord	2025-07-07 22:01:59 +00:00
Nathan Whitaker	51c43ce8b4	fix(bundle): make the "dynamic require" hack work on minified output (#29997) ... It's terrible and I hate it but it works	2025-07-04 02:11:09 +00:00
David Sherret	cfa5273096	refactor: ability to preserve jsx internally (#29994)	2025-07-03 21:39:54 +00:00
Nathan Whitaker	c5d06179a1	fix(bundle): resolve "sloppy imports" in npm packages when bundling (#29989) ... Fixes a case reported in discord. At runtime node (and us) would fail on this, but all major bundlers permit this. So as a fix, just allow it during bundling only.	2025-07-03 12:46:45 -07:00
David Sherret	c1751d7ef4	refactor: extract PreparedModuleLoader from CLI (#29977) ... Extracts out a `PreparedModuleLoader` from the cli's `ModuleLoader`. This is specific to loading from the `ModuleGraph`.	2025-07-03 14:11:46 -04:00
Nathan Whitaker	9379a74e08	chore: update to edition 2024 (#29923)	2025-07-02 17:59:39 -07:00
Nathan Whitaker	0470cb3ada	fix(serve): actually wire up resolving main module with import map for deno serve (#29974) ... Closes https://github.com/denoland/deno/issues/29897	2025-07-02 11:29:23 -07:00
David Sherret	7a1e949c47	refactor: extract DenoDir, Emitter, EmitCache and ParsedSourceCache from cli crate (#29961)	2025-07-02 08:56:02 -04:00
David Sherret	3ae11d889a	fix(publish): disallow publishing with bytes or text imports (#29954)	2025-07-01 15:47:54 +00:00
Bartek Iwańczuk	f6176a1674	feat: add support for --preload/--import flag (#29626) ... This commit adds initial support for `--preload` (aliased to `--import`) flag that allows to load and execute multiple ES modules before the entry point modules is executed. This command is available in `deno run`, `deno test` and `deno bench` subcommands. Closes https://github.com/denoland/deno/issues/29776	2025-07-01 16:21:00 +05:30
Nathan Whitaker	033da85781	chore(bundle): rename --one-file to --inline-imports (#29946)	2025-06-30 23:13:32 +00:00
Kingsword	64525d289a	feat(fmt): remove UTF-8 BOM instead of maintaining it (#29796) ... Co-authored-by: David Sherret <dsherret@users.noreply.github.com>	2025-06-28 00:50:22 -04:00
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
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
David Sherret	4a0cd18a6b	fix(install/global): resolve bin name from npm packument (#29884)	2025-06-25 15:10:26 -04: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	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
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
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
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
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
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	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	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
Leo Kettmeir	9ef98862eb	fix(install): infer name from @scope/cli pattern (#29694)	2025-06-12 16:37:34 +02:00
Bartek Iwańczuk	b64d4cb125	fix(bundle): don't panic on broken pipe (#29706) ... `deno bundle main.js | less` and then `Ctrl + C` caused a panic because of `Broken pipe` error.	2025-06-11 19:05:28 +00:00
David Sherret	b3242183f3	refactor: extract TsConfigResolver to deno_resolver (#29695) ... Towards adding support for emitting in deno_resolver.	2025-06-10 18:36:16 -04:00