Skip to content

chore: fix instantiation of async context to use variable in use cases #131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 23, 2025
Merged

chore: fix instantiation of async context to use variable in use cases #131

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions USE-CASES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,7 +127,7 @@ sync and async execution by keeping track of the context in which we started the
execution.

```typescript
const context = new AsyncContext();
const context = new AsyncContext.Variable();

export function log() {
const currentId = context.get();
Expand Down Expand Up @@ -158,7 +158,7 @@ doc.addEventListener('click', () => {
});
});
// Some framework code
const context = new AsyncContext();
const context = new AsyncContext.Variable();
function patch(doc, data) {
doLotsOfWork(doc, data, update);
}
Expand Down Expand Up @@ -237,7 +237,7 @@ doc.addEventListener('click', () => {
});
});

const context = new AsyncContext();
const context = new AsyncContext.Variable();
function patch(dom, data) {
doLotsOfWork(dom, data, update);
}
Expand Down Expand Up @@ -343,7 +343,7 @@ Read more at [opentelemetry/fetch](https://github.com/open-telemetry/opentelemet

## Use Case: Running servers in service workers

A typical web app has a server-side component and a client-side component. Many web frameworks (Next, Nuxt, SvelteKit etc) are designed in such a way that both halves can be built from a single codebase.
A typical web app has a server-side component and a client-side component. Many web frameworks (Next, Nuxt, SvelteKit etc) are designed in such a way that both halves can be built from a single codebase.

One request that framework maintainers often receive is for the ability to run the server, or at least part of it, in a service worker. Barring any dependencies on sensitive information that should not be accessible to users, or packages that only run in a server environment, this can be a successful strategy for building low-latency apps that are resilient in the face of poor network conditions.

Expand Down