This is a breaking change that wasn't called out in the release notes, if I'm using these functions, what should I used instead
?

Sorry this didn't end up highlighted as a breaking change in the release notes.

What are you using these exports for?

I was using them to pass an event to captureEvent. Is there a preferred alternative for constructing an event to pass to that method?

Hey @maclockard - thanks for reaching out. Here we expect folks you to just directly use captureException or captureMessage instead of doing captureEvent(eventFromException(new Error('example')).

Why are you preferring to use captureEvent here? captureEvent is meant for use cases where you directly set attributes using the event payload docs and our TypeScript types.

Why make folks who are manually setting some of the event fields manually set all of them? What I was doing was using the event builder methods to make an event then overriding some fields manually before capturing.

We recommend folks use beforeSend, or our event processor API to accomplish mutating events. For example:

const myError = new Error(...);

Sentry.withScope((scope) => {
  scope.addEventProcessor(event => {
    if (badCondition) {
      // don't send event to Sentry
      return null;
    }

    event.X = ...
    event.Y = ...
    return event;
  });
  Sentry.captureException(myError);
});

We intentionally constrain the top level API surface so that we can more easily make improvements and changes without user impact.

Both eventFromException and eventFromMessage were undocumented APIs - they do not show up on https://docs.sentry.io