staytuned_team Posts

staytuned_team

•Created by staytuned_team on 11/15/2024 in #help

Issue with deno emit bundle in Workspaces - Need Help and Documentation

Hi everyone, I'm having trouble with deno emit bundle function, when my project is in workspaces. It seems like the bundling process doesn't support workspaces. Has anyone encountered this issue before and can provide an example of how to handle this use case? Are there any official docs available that address this? taking example from the official deno workspace docs: https://docs.deno.com/runtime/fundamentals/workspaces/ and deno/emit docs: https://jsr.io/@deno/emit after creating the files mentioned in the doc, i.e.:

/
├── deno.json
├── main.ts
├── add/
│     ├── deno.json
│     └── mod.ts
└── subtract/
      ├── deno.json
      └── mod.ts

/
├── deno.json
├── main.ts
├── add/
│     ├── deno.json
│     └── mod.ts
└── subtract/
      ├── deno.json
      └── mod.ts

add two files 1. import_map.json 2. bundle.ts // bundle.ts:

import { bundle } from "jsr:@deno/emit";
const result = await bundle(
  "./main.ts",
  {
    importMap: "./import_map.json"
  }
);

const { code } = result;
console.log(code);

import { bundle } from "jsr:@deno/emit";
const result = await bundle(
  "./main.ts",
  {
    importMap: "./import_map.json"
  }
);

const { code } = result;
console.log(code);

the following error occures which bundling:

error: Uncaught (in promise) Error: Unable to output during bundling: load_transformed failed: failed to analyze module: failed to resolve @scope/add from file:///C:/Users/ASUS/Downloads/emit/main.ts: Cannot resolve "@scope/add" from "file:///C:/Users/ASUS/Downloads/emit/main.ts".

error: Uncaught (in promise) Error: Unable to output during bundling: load_transformed failed: failed to analyze module: failed to resolve @scope/add from file:///C:/Users/ASUS/Downloads/emit/main.ts: Cannot resolve "@scope/add" from "file:///C:/Users/ASUS/Downloads/emit/main.ts".

Thanks in advance for your help!

7 replies

DDeno

•Created by staytuned_team on 11/13/2024 in #help

does deno_graph natively resolve the path of workspaces?

Hi everyone, I'm working on a project that includes multiple workspace members defined in my deno.json file using the workspaces field. I'm using deno_graph to resolve dependencies, but I noticed that while it allows specifying an import_map, there's no option to include the deno.json file directly. Does deno_graph natively understand and resolve workspaces specified in deno.json? If so, how can I configure it to resolve dependencies across all workspace members? If not, what would be the recommended approach to handle dependencies in a multi-workspace setup using deno_graph? Any guidance would be greatly appreciated! reference: deno_grpah jsr Thank you.

6 replies