@sentry/nextjs: can't read data inside next-compose-plugins

• Review the documentation: https://docs.sentry.io/
• Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• Use the latest release: https://github.com/getsentry/sentry-javascript/releases
• Provide a link to the affected event from your Sentry account

Package + Version

• @sentry/browser
• @sentry/node
• raven-js
• raven-node (raven for node)
• other: @sentry/nextjs

Version:

"@sentry/nextjs": "^6.4.1",
"next": "^10.2.1",

Description

FYI: We start projects with version < 10.0.0 and then we are upgrading to the latest version.

Previously we have a setting in our next.config.js like this.

const withCss = require("@zeit/next-css");
const withSass = require("@zeit/next-sass");
const withPlugins = require("next-compose-plugins");
const withImages = require("next-images");

module.exports = withPlugins([withCss, withSass, withImages], {
    env: {
        SENTRY_DSN: "xxx",
    }
});

Then we change the structure like in the documentation, become like this:

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

const withCss = require("@zeit/next-css");
const withSass = require("@zeit/next-sass");
const withPlugins = require("next-compose-plugins");
const withImages = require("next-images");

const moduleExports = withPlugins([withCss, withSass, withImages], {
    env: {
        SENTRY_DSN: "xxx",
    }
});

// other codes

module.exports = withSentryConfig(moduleExports, SentryWebpackPluginOptions);

When we run the app, env can’t read with a struct like that. (start from this we are confused)

But, when we are changing the structure like this:

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

const moduleExports = {
    env: {
        SENTRY_DSN: "xxx",
    }
};

// other codes

module.exports = withSentryConfig(moduleExports, SentryWebpackPluginOptions);

The app can run fine, but the problem is we don’t want to change like that because we are still using the next-compose-plugins.

Is there any recommendation for us, thank you.

[Sm1t]

@AbhiPrasad hi, it looks like SentryWebpackPluginOptions is being ignored when using withSentryConfig inside withPlugins. Reproduction:

• clone https://github.com/vercel/next.js/tree/canary/examples/with-sentry
• add the following next.config.js:

const { withSentryConfig } = require('@sentry/nextjs');
const withPlugins = require('next-compose-plugins');

const SentryWebpackPluginOptions = {
  release: 'qwe',
  dryRun: false,
};

module.exports = withPlugins(
  [[withSentryConfig, SentryWebpackPluginOptions]],
  {}
);

• yarn dev
• release still “development” (terminal: [Sentry Webpack Plugin] Finalizing release: ‘development’), uploading source maps to Sentry was not called

When using withSentryConfig outside of plugins, as in the example above, SentryWebpackPluginOptions works as expected - release ‘qwe’, loading source maps into Sentry was called (terminal: ‘Authentication credentials were not provided’, as expected)

const { withSentryConfig } = require('@sentry/nextjs');
const withPlugins = require('next-compose-plugins');

const SentryWebpackPluginOptions = {
  release: 'qwe',
  dryRun: false,
};

module.exports = withPlugins(
  [],
  withSentryConfig({}, SentryWebpackPluginOptions)
);

[lobsterkatie]

Unfortunately all of our resources this quarter have been aimed at getting our new major out the door, so I haven’t gotten a chance to work on this any more.

(I’m sorry - I know that’s not a super satisfying answer. Once the major’s out, I can bring this up again with the team.)