65 commits

Author	SHA1	Message	Date
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
David Sherret	f2129e4f94	perf: bust emit cache only on deno_ast version change (#29984) ... The emit cache is pretty stable nowadays, so we could probably just cache bust whenever the deno_ast version changes instead of the CLI version. This will also allow stuff like deno-js-loader to reuse cached emits.	2025-07-03 12:59:29 -04:00
Nathan Whitaker	9379a74e08	chore: update to edition 2024 (#29923)	2025-07-02 17:59:39 -07:00
David Sherret	efac7cd67a	refactor: extract CJS analysis from CLI crate (#29975) ... Moves the `CliCjsCodeAnalyzer` out of the CLI crate and into deno_resolver.	2025-07-02 15:31:25 -04:00
David Sherret	7a1e949c47	refactor: extract DenoDir, Emitter, EmitCache and ParsedSourceCache from cli crate (#29961)	2025-07-02 08:56:02 -04:00
denobot	45dfae18ee	2.4.0 (#29959) ... Co-authored-by: dsherret <dsherret@users.noreply.github.com>	2025-07-01 16:21:05 -04:00
David Sherret	2bb734f7a3	perf: skip loading bytes and text imports into memory when already cached and building module graph (#29931) ... This makes it so that if the bytes and text imports are already cached it won't load them into memory until actually loading the module with deno_core.	2025-06-28 12:22:21 +02: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
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
David Sherret	ec32c6e5ba	feat(unstable): bytes and text imports (#29855)	2025-06-26 11:21:16 -04: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
Nayeem Rahman	470aa51886	refactor: rename ts_config to compiler_options (#29769)	2025-06-17 02:07:43 +01: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	090df40290	refactor: add deno_package_json crate (#29743)	2025-06-13 22:55:12 +00:00