Ensure. `Sentry.captureUserFeedback(feedback)` is exported from node packages

[alexavil]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/node

SDK Version

7.106.1

Framework Version

No response

Link to Sentry event

No response

SDK Setup

  Sentry.init({
    dsn: "https://d7c06763ec24990c168e4ad0db91e360@o4504711913340928.ingest.sentry.io/4505981661151232",
    tracesSampleRate: 1.0,
    profilesSampleRate: 1.0,
    integrations: [
      new Sentry.Integrations.Http({ tracing: true }),
      new nodeProfilingIntegration(),
    ],
    environment: debug ? "testing" : "production",
    release: "3.0",
  });

Steps to Reproduce

I copied the following example from the Node.js documentation page for User Feedback:

import * as Sentry from "@sentry/node";

const eventId = Sentry.captureMessage("User Feedback");
// OR: const eventId = Sentry.lastEventId();

const userFeedback = {
  event_id: eventId,
  name: "John Doe",
  email: "john@doe.com",
  comments: "I really like your App, thanks!",
};
Sentry.captureUserFeedback(userFeedback);

Expected Result

User Feedback should be captured properly.

Actual Result

TypeError: Sentry.captureUserFeedback is not a function

Looks like this function is missing from the @sentry/node package, but the documentation says Node.js is supported.

[mydea]

Hey,

yes you are right, this is not exported right now from node - sorry about the confusion!
We'll add an export for this in an upcoming release - we are generally overhauling user feedback right now, so while working on this I'll try to make sure to export it everywhere we need it!

[alexavil]

@mydea Thanks, any workaround until the new release?

[mydea]

@mydea Thanks, any workaround until the new release?

Sadly, not really, as this currently only lives in the browser package. We probably should "fix" the docs until we have a better solution for this 😬