Jack Williams

It's a mentioned issue, but commenting to highlight it. @MonsterDeveloper just exposed `InngestFunction#createExecution()` over at #618, released in [3.19.16](https://github.com/inngest/inngest-js/pull/621). Note that it's an internal method that can still change at...

Please see inngest/inngest#1680 for further conversation and progress on this. 🙂 - inngest/inngest#1680

There's a preliminary PR for this over at #657. Leaving this issue open to continue to gather feedback, but you can use that PR to get going now if you...

Hi, @mcky! 👋 Thanks loads for this detailed write-up. I believe you _should_ be able to bring your own child-compatible logger if you pass a logger with a `.child()` when...

This is shipped in [`3.18.1`](https://github.com/inngest/inngest-js/releases/tag/inngest%403.18.1) following #549. Thanks, @maktouch! I'm also noting https://github.com/inngest/inngest-js/pull/549#issuecomment-2070205258, which highlights how rubbish the stack trace is for this instance: no usable lines and the `prettyError`...

Hi, @gramliu 👋 Thanks for the detailed report! We've seen this recently but thought we had a fix for it. Is this only happening for you in production or with...

Hi @mcky! 👋 Ah - this is a perfect use case and something we want to get right for middleware to make sure it's not restrictive. The debugging middleware in...

@fritzblue Progress for this being tracked here 🙂 - #106

@fritzblue A version of this is up if you `npm install inngest@solid`. Need to add it to the suite of integration tests and add docs, but would love for you...

Removed Renovate in #608.