Can you guys update your example to include a custom express.js server? The Next.js example you have is too trivial for real world situations so it'd be much more helpful to show how to use bugsnag in cases where you'd have custom routes being served by express. (I know that API routes exist now. but they didn't exist before so it'd be nice to show case common use cases within Next.js)

We're cu

Description

A lot of console.warn yellow warning message when the data pass to leaveBreadcrumbs contains functions.

Describe the solution you'd like

This feature will resolve issue #126. See this comment for details.

Add an option to SentryAspNetCoreOptions named FlushOnCompletedRequest of type bool and a FlushTimeout with default value of `Timestam

Looks like we have some users where the "Less Scary" dialog doesn't show the buttons.
They are moved down and out of sight.