13 commits

Author	SHA1	Message	Date
David Sherret	6ca54279de	refactor: add deno_maybe_sync crate (#30459) ... Extracted out of https://github.com/denoland/deno/pull/30330 This is to reduce code duplication.	2025-08-20 08:53:30 -04:00
Kendell R	75f1a9d5de	fix(resolver): update "with --unstable-sloppy-imports" message to use "--sloppy-imports" (#30421)	2025-08-18 13:59:27 -04:00
David Sherret	b77b0be068	refactor(resolver): improve and expose details of CouldNotResolveError (#30410) ... Need this for deno-js-loader.	2025-08-14 20:31:39 +00:00
林炳权	68297b5f10	chore: Rust 1.89.0 (#30364) ... Related PR: https://github.com/denoland/deno/pull/30354	2025-08-09 11:11:48 +00:00
David Sherret	afe149e071	fix(bundle): require of sub directory in npm package should consult package.json (#30253)	2025-07-31 14:48:51 +00:00
snek	8551e18d72	fix(http): catch more tunnel close errors (#30236) ... Handles more error cases when tunnels close. this logic got super nasty to do as nested if statements, so i added recursion >:)	2025-07-29 23:37:04 +02:00
David Sherret	9dbf414813	fix(check): ensure module not found errors are surfaced (#30181) ... Closes https://github.com/denoland/deno/issues/30116	2025-07-23 17:57:08 -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	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
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	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

Renamed from libs/deno/graph.rs (Browse further)