sentry-javascript: TypeError: withSentryConfig is not a function

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which package are you using?

@sentry/nextjs

SDK Version

7.8.1

Framework Version

“react”: “^17.0.2”, “next”: “^11.1.2”,

Link to Sentry event

No response

Steps to Reproduce

  1. add sentry to nextjs application. https://docs.sentry.io/platforms/javascript/guides/nextjs/
  2. update next.config.js
// This file sets a custom webpack configuration to use your Next.js app
// with Sentry.
// https://nextjs.org/docs/api-reference/next.config.js/introduction
// https://docs.sentry.io/platforms/javascript/guides/nextjs/

const { withSentryConfig } = require('@sentry/nextjs');

const moduleExports = {
  // Your existing module.exports
  reactStrictMode: true,
  swcMinify: true,
};

const sentryWebpackPluginOptions = {
  // Additional config options for the Sentry Webpack plugin. Keep in mind that
  // the following options are set automatically, and overriding them is not
  // recommended:
  //   release, url, org, project, authToken, configFile, stripPrefix,
  //   urlPrefix, include, ignore

  silent: true, // Suppresses all logs
  // For all available options, see:
  // https://github.com/getsentry/sentry-webpack-plugin#options.
};

// Make sure adding Sentry options is the last code to run before exporting, to
// ensure that your source maps include changes from all other Webpack plugins
module.exports = withSentryConfig(moduleExports, sentryWebpackPluginOptions);

  1. run yarn dev

Expected Result

App should start

Actual Result

localhost:3001 shows the following error in chrome. Screen Shot 2022-08-02 at 5 40 42 AM

Terminal does not show the error.

Screen Shot 2022-08-02 at 5 52 03 AM

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 3
  • Comments: 24 (11 by maintainers)

Most upvoted comments

I’m trying to upgrade from 7.30.0 to 7.43.0 but when I try to upgrade, it throws this error while building.

@prateekjain98 and I managed to fix this by deleting our yarn.lock and installing dependencies again. Not sure what exactly fixed it, but my guess is that there was a mix of dependencies installed through yarn install and npm install that caused dependency issues.

For future people who encounter this error: I fixed this by converting my next.config.js file into next.config.mjs. This allowed me to do the sentry import like so: const { withSentryConfig } = await import('@sentry/nextjs');

Then export the config like so: export default withSentryConfig(nextConfig, sentryWebpackPluginOptions);

The issue seems to be that the Sentry configuration requires that you do a module import, which isn’t supported by a regular next.config.js. See the next.js docs on the config file here.