Jack Williams
Jack Williams
## Description WIP - [ ] When a function with no steps errors but recovers before exhausting retries, create a separate "Function errored" node ## Motivation ## Type of change...
## Summary Read the incoming headers tracestate and traceparent. If it is set, copy the header to any outgoing event-sending requests. This only covers `step.sendEvent()`; we'll add later support for...
## Summary Step returns use the `Jsonify` type to represent the result of a step being (de)serialized as it is passed to and from Inngest. If `strictNullChecks: false` is set...
## Summary When the library emits a log to try and help the user diagnose or resolve an issue, we usually include a stack trace in order to provide them...
## Summary The Sentry middleware example on the docs has a few issues: * It runs `Sentry.init()` - most users will already be initializing the client, and initializing it again...
**Describe the bug** When using [`basePath`](https://nextjs.org/docs/app/api-reference/next-config-js/basePath) in a `next.config.js` file, the `"inngest/next"` serve handler doesn't detect the correct URL. **To Reproduce** 1. Add `basePath: "/example"` to `examples/framework-nextjs/next.config.js` 2. Run `pnpm...
## Summary Incorrect properties would be ignored and produce no type errors when creating a client via `new Inngest()`. For example, the following would show no errors, even though `baseURL`...
## Summary When creating middleware, include all internal "built-in" middleware typing, allowing users to access types such as `logger` to make changes and corrections. ```ts new InngestMiddleware({ name: "Example Middleware",...
## Summary Adds streaming capabilities to to the `"inngest/cloudflare"` serve handler. ## Checklist - [ ] Added a [docs PR](https://github.com/inngest/website) that references this PR - [ ] Added unit/integration tests...