Bhaumin
Bhaumin
DDeno
Created by Bhaumin on 12/5/2024 in #help
why deno vs code extension not supporting deno test describe and coverage?
Any ETA for this to lift up DX with deno?
6 replies
DDeno
Created by Bhaumin on 12/5/2024 in #help
why deno vs code extension not supporting deno test describe and coverage?
@dsherret any idea, or solution or i need to create issue?
6 replies
DDeno
Created by Bhaumin on 12/5/2024 in #help
why deno vs code extension not supporting deno test describe and coverage?
6 replies
DDeno
Created by Bhaumin on 11/16/2024 in #help
Understanding deno test Behavior with Interdependent Modules
ok thanks for clarity
25 replies
DDeno
Created by staytuned_team on 11/15/2024 in #help
Issue with deno emit bundle in Workspaces - Need Help and Documentation
alright thanks
7 replies
DDeno
Created by Bhaumin on 11/16/2024 in #help
Understanding deno test Behavior with Interdependent Modules
@Doctor 🤖 this one
25 replies
DDeno
Created by Bhaumin on 11/16/2024 in #help
Understanding deno test Behavior with Interdependent Modules
Directly acyclic graph
25 replies
DDeno
Created by Bhaumin on 11/16/2024 in #help
Understanding deno test Behavior with Interdependent Modules
it can be automated if the deno project is fully in workspace manner and by using deno_graph for this and then all test cases can be executed automatically in the required dag manner? After implementing such a feature only i am asking, is it possible right?
25 replies
DDeno
Created by Bhaumin on 11/16/2024 in #help
Understanding deno test Behavior with Interdependent Modules
Okay got it, but is there any way to achieve this or needs to be implemented as a core feature in the deno cli test?
25 replies
DDeno
Created by Bhaumin on 11/16/2024 in #help
Understanding deno test Behavior with Interdependent Modules
it's in workspace, then it is possible? or any other way?
25 replies
DDeno
Created by Bhaumin on 11/16/2024 in #help
Understanding deno test Behavior with Interdependent Modules
any work in progress or issue/pr to track work if no then should i create issue? i think cli is already using deno_graph and that features can be extended to deno test also...so what you suggest?
25 replies
DDeno
Created by Bhaumin on 11/16/2024 in #help
Understanding deno test Behavior with Interdependent Modules
No description
25 replies
DDeno
Created by Bhaumin on 11/16/2024 in #help
Understanding deno test Behavior with Interdependent Modules
ok i will share. thanks for support
25 replies
DDeno
Created by Bhaumin on 11/16/2024 in #help
Understanding deno test Behavior with Interdependent Modules
yes and in dag manner
25 replies
DDeno
Created by Bhaumin on 11/16/2024 in #help
Understanding deno test Behavior with Interdependent Modules
ok but dag manner test cases execution possible right now?
25 replies
DDeno
Created by staytuned_team on 11/15/2024 in #help
Issue with deno emit bundle in Workspaces - Need Help and Documentation
@bartlomieju Please help to solve...thanks
7 replies
DDeno
Created by staytuned_team on 11/15/2024 in #help
Issue with deno emit bundle in Workspaces - Need Help and Documentation
Can you please review updated question and help if you can?
7 replies
DDeno
Created by staytuned_team on 11/13/2024 in #help
does deno_graph natively resolve the path of workspaces?
ok
6 replies
DDeno
Created by staytuned_team on 11/13/2024 in #help
does deno_graph natively resolve the path of workspaces?
is this correct i asked in ai in deno docs website? To configure a Deno workspace that can be resolved using the Deno graph, you need to set up a deno.json file at the root of your workspace. This file should define the workspace members and any necessary imports. Here’s an example of how your deno.json file might look:
{
"workspace": ["./add", "./subtract"],
"imports": {
"chalk": "npm:chalk@5"
}
}
{
"workspace": ["./add", "./subtract"],
"imports": {
"chalk": "npm:chalk@5"
}
}
In this configuration, the workspace key specifies the directories that contain your workspace members, such as add and subtract. The imports key allows you to define any external dependencies that your workspace will use. Each workspace member can also have its own deno.json file. For example, in the add directory, you might have:
{
"name": "@scope/add",
"version": "0.1.0",
"exports": "./mod.ts"
}
{
"name": "@scope/add",
"version": "0.1.0",
"exports": "./mod.ts"
}
This setup allows you to reference the workspace members using bare specifiers in your code. For instance, in your main.ts file, you can import the functions from the workspace members like this:
import chalk from "chalk";
import { add } from "@scope/add";
import { subtract } from "@scope/subtract";

console.log("1 + 2 =", chalk.green(add(1, 2)));
console.log("2 - 4 =", chalk.red(subtract(2, 4)));
import chalk from "chalk";
import { add } from "@scope/add";
import { subtract } from "@scope/subtract";

console.log("1 + 2 =", chalk.green(add(1, 2)));
console.log("2 - 4 =", chalk.red(subtract(2, 4)));
To visualize the dependencies and how they connect within your workspace, you can use the Deno graph command:
deno graph
deno graph
This command will generate a graph of your module dependencies, showing how everything is interconnected within your workspace. It provides a clear view of the relationships between your modules and their imports.
6 replies
DDeno
Created by staytuned_team on 11/13/2024 in #help
does deno_graph natively resolve the path of workspaces?
@bartlomieju @kitsonk @dsherret Any solution? Please help
6 replies