Support an instrumentation preload for the Nest queue consumer
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- node.js, typescript
- Domain
- backend, observability
Research direction
Read the Nest queue consumer generation path in @workflow/nest and the workflow-nest build --vercel CLI options, then trace how the consumer, workflow, and step bundles are built. Check the lifecycle-hook documentation and local development behavior. Done means a supported preload runs once per function instance before consumer and step modules, is included in the generated function, and has documented bundle and local development behavior.
Written by the indexing model from the issue text.
Description
Problem
A Nest application deployed with workflow-nest build --vercel runs Workflow's queue consumer in a standalone function that does not load the Nest application's bootstrap or instrumentation module. As a result, an application cannot use its existing OpenTelemetry and error-reporting setup in that function through a documented configuration hook.
The Workflow lifecycle-hook documentation says application startup registration is not supported for the standalone Nest function and cautions against registering at a workflow file's top level. The workflow-nest build CLI does not expose a preload, instrumentation entry, or bundle injection option.
Request
Provide a supported instrumentation or preload entry for the generated Nest queue consumer. It should execute once per function instance before the consumer and step modules, allow an application to register its OpenTelemetry provider and error-reporting integration idempotently, and be bundled with the generated function. Please document how it interacts with the separate workflow and step bundles and local development.
Environment
@workflow/nest5.1.4workflow5.2.3@workflow/builders5.0.6- Vercel Node.js functions
A supported entry would remove the need for each application to arrange a shared step-side import or patch generated build output.
- Dominant language
- TypeScript
- Stars
- 2.5k
- Forks
- 401
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 201
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vercel/workflow
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
node-module-esbuild-plugin: getImportedIdentifier only checks the first named import when locating a violationPossibly taken @div-cowboy claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel/workflow#5057 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
code-transform.mdx §ID Generation omits the package-shipped `name@version` ID formPossibly taken @Mohith26 claimed this 113 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
Similar issues
-
db-d1-sqlite: upsert is aliased to updateOne, so payload.kv.set never inserts new keysPossibly taken @pcbeingused333 claimed this today. OpenBug db: d1-sqlite Payload OSS
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
payloadcms/payload#19766 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
device-management-toolkit/sample-web-ui#3711 ·
Maintainers usually reply within 1 day
-
bug impact:low Team: SecuritySolution Team:Defend Workflows v9.6.0
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
elastic/kibana#306401 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
agentes-chat/agentes-chat#927 ·
Maintainers usually reply within 1 day
-
Closing a pinned tab jumps to the Tabs section instead of the next open pinned tabPossibly taken @seenimohamed claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ardia-browser/ardia#2769 ·
Maintainers usually reply within 1 day