inngest@3.2.1

Patch Changes

• #360 260dd75 Thanks @jpwilliams! - Inngest errors now appear more succintly in UIs, free of ANSI codes and verbose information

inngest@3.1.1

Patch Changes

• #354 e2f68d6 Thanks @jpwilliams! - Fix path matching types getting lost in certain recursive event types

• #350 933b998 Thanks @jpwilliams! - Separate Zod typing from library, enabling minor-agnostic versioning support

inngest@3.1.0

Minor Changes

• #338 ef35fea Thanks @jpwilliams! - Add debounce configuration option. See Debounce documentation for more information.

Patch Changes

• #337 672c428 Thanks @jpwilliams! - Ensure fromRecord<>() doesn't accept clashing names

inngest@3.0.2

Patch Changes

• #348 ebb245f Thanks @jpwilliams! - Fix "inngest/next" types not inferring from defineProperties

• #346 c14bbb3 Thanks @jpwilliams! - Fix waitForEvent potentially dropping some fields when being parsed

inngest@3.0.1

Patch Changes

• #339 bf8b004 Thanks @jpwilliams! - Bump next to 13; keep up-to-date with their only supported major to support typing

• #343 77c7f66 Thanks @tonyhb! - Allow steps to execute with null data

inngest@3.0.0

Major Changes

• #294 f2f4856 Thanks @jpwilliams! - Clients and functions now require IDs

  When instantiating a client using new Inngest() or creating a function via inngest.createFunction(), it's now required to pass an id instead of a name.

  Previously only name was required, but this implied that the value was safe to change. Internally, we used this name to produce an ID which was used during deployments and executions.

  See the v3 migration guide.

• #294 f2f4856 Thanks @jpwilliams! - Refactored available environment variables and configuration

  The arrangement of environment variables available has shifted a lot over the course of v2, so in v3 we've streamlined what's available and how they're used.

  See the v3 migration guide.

• #294 f2f4856 Thanks @jpwilliams! - In v2, providing a fns option when creating a function -- an object of functions -- would wrap those passed functions in step.run(), meaning you can run code inside your function without the step.run() boilerplate.

  This wasn't a very well advertised feature and had some drawbacks, so we're instead replacing it with some optional middleware.

  See the v3 migration guide.

• #294 f2f4856 Thanks @jpwilliams! - Serving functions could become a bit unwieldy with the format we had, so we've slightly altered how you serve your functions to ensure proper discoverability of options and aid in readability when revisiting the code.

  See the v3 migration guide.

• #294 f2f4856 Thanks @jpwilliams! - Shorthand function creation removed

  inngest.createFunction() can no longer take a string as the first or second arguments; an object is now required to aid in the discoverability of options and configuration.

  See the v3 migration guide.

• #294 f2f4856 Thanks @jpwilliams! - All steps require IDs

  When using any step.* tool, an ID is now required to ensure that determinism across changes to a function is easier to reason about for the user and the underlying engine.

  The addition of these IDs allows you to deploy hotfixes and logic changes to long-running functions without fear of errors, failures, or panics. Beforehand, any changes to a function resulted in an irrecoverable error if step definitions changed. With this, changes to a function are smartly applied by default.

  See the v3 migration guide.

Patch Changes

• #333 67bda66 Thanks @goodoldneon! - (Internal) Fix missing name on NonRetriableError, ensuring it's correctly (de)serialized

inngest@2.7.2

Patch Changes

• #323 3b2efa6 Thanks @jpwilliams! - Better error handling for .sendEvent() errors from Inngest API, ensuring easier debugging when failing to send events - partial of #256

inngest@2.7.1

Patch Changes

• #325 b8858c9 Thanks @jpwilliams! - Hotfix: Ensure ProxyLogger (and some other used classes/types) is correctly exported from "inngest"

inngest@2.7.0

Minor Changes

• #313 32c34b3 Thanks @jpwilliams! - Add ability to declare and send events without payloads, e.g. inngest.send({ name: "my.event" });

• #310 696c411 Thanks @michealroberts! - Added h3 framework server handler

Patch Changes

• #319 71b7d26 Thanks @jpwilliams! - Add ESM exports to inngest package to avoid extension imports

inngest@2.6.1

Patch Changes

• #312 ca6d6aa Thanks @mmachatschek! - chore: update cross-fetch to ^4.0.0 package