jon

PostsComments

DDeno

•Created by jon on 9/19/2024 in #help

AsyncLocalStorage without `node:async_hooks`

OK, I think that'll be a blocker for my use case... as a workaround, if it is possible already to host a private instance of JSR, that could also work.

8 replies

DDeno

•Created by jon on 9/19/2024 in #help

AsyncLocalStorage without `node:async_hooks`

I see. Given that, is there another way to import Deno's AsyncLocalStorage other than through node:async_hooks? Particularly, I am interested in avoiding deno_emit errors related to using node:

8 replies

DDeno

•Created by wilsonlewis on 9/9/2024 in #help

Workspace member parallel processes (monorepo)

@wilsonlewis as a workaround, you could do something like: - make a task in your root deno.json[c], that itself runs a workspace-task.ts file with some {taskName} parameter - in workspace-task.ts , read the workspace array from your root deno.json[c] - iterate through and cwd's into each workspace directory, reads the deno.json[c] there - for each matching {taskName}, run deno task {taskName}

4 replies

DDeno

•Created by yoggyd on 9/4/2024 in #help

any reason against using the deps.ts approach?

I’m stuck on an embedded deno 1.38.1 for now, so JSR isn’t an option quite yet. I have been trying out using import maps, and resolving jsr-like e.g. @std/async names to https/deno.land. Are there any major differences between this and using JSR? I was thinking it’d let me get most of the benefits without having to upgrade deno, or at least make the transition pretty easy once I do. Thoughts?

7 replies

DDeno

•Created by mavdotjs on 7/7/2024 in #help

Workspace option inconsistency?

I was playing around with workspaces today, and I also encountered inconsistencies. For example, deno_std repository uses "workspaces", but the JSONSchema file that VSCode uses for deno.json references "workspace". I just use both right now.

8 replies