deno_graph
deno_graph copied to clipboard
denoland
The module graph logic for Deno CLI
```js // main.ts import config from "./deno.json" assert { type: "json" }; const obj = { config }; export default obj; ``` ```json // deno.json { "compilerOptions": { "jsx": "react-jsx",...
When validating a graph and reaching a type branch, current behaviour descends into the children imports, treating them as code imports, and therefore erroring when there is a type branch...
`ModuleGraphError` and `ResolutionError` did not implement `Error::source()`, so if a user-provided `Resolver` or `Loader` returns an error, its cause chain is lost. This PR implements `source()`, but it keeps the...
There exists `TS2822 [ERROR]: Import assertions cannot be used with type-only imports or exports.`, so we shouldn't check assertions for type-only imports. https://github.com/denoland/deno/issues/14913
This is a pre-requisite for WASM imports that additionally allows us to minimize clones when doing things like BOM stripping.
The previous example did not compile for me. I'm not sure if this is the actual minimal example, but it now runs.
Previously, if a specifier was imported more than once, with conflicting assertions, we'd only really consider the final import. This is wrong: conflicting assertions are an error in-themselves already. I...
Previously module source was represented as `String`. This does not work for non-textual formats like WASM. As such, module source is now represented as `[u8]`. In JS, the module source...
This commit adds support for WebAssembly modules in the graph. Imports inside of the WebAssembly are parsed out using `wasmparser`, and are further analyzed by the graph like other dependencies....
To unblock https://github.com/denoland/deno/issues/2552, `deno_graph` needs to be able to represent WASM modules in a module graph. To do this, we need to parse out the [`import`](https://webassembly.github.io/spec/core/syntax/modules.html#syntax-import) sections in a module,...