Nextjs - Source mapping failed: A source map could not be applied

Anyone using Next.js and has successfully managed to upload source maps to bugsnag?

I have successfully set up my next.config.js file to upload my source maps to bugsnag using webpack-bugsnag-plugins.

However, bugsnag cannot seem to apply the source map to my code as seen in the screenshot below. Also, release stage is recorded as Production even though the issue is triggered from Staging (I’ve tried setting bugsnag releaseStage to process.env.NODE_ENV and it does not work).

next.config.js

const fs = require('fs')
const withSass = require('@zeit/next-sass')
const { BugsnagSourceMapUploaderPlugin } = require('webpack-bugsnag-plugins')

module.exports = withSass({
  webpack: (config, { buildId, dev, isServer }) => {
    const oldEntry = config.entry
    config.entry = function () {
      return oldEntry().then(function (entries) {
        if (entries['main.js']) {
          entries['main.js'].unshift('babel-polyfill')
        }

        return entries
      })
    }

    config.module.rules = config.module.rules.map(rule => {
      if (rule.loader === 'babel-loader') {
        rule.options.cacheDirectory = false
      }
      return rule
    })

    config.devtool = 'source-map'
    for (const plugin of config.plugins) {
      if (plugin['constructor']['name'] === 'UglifyJsPlugin') {
        plugin.options.sourceMap = true
        break
      }
    }

    config.plugins.push(
      new BugsnagSourceMapUploaderPlugin({
        apiKey: 'af3a166c839bf6a0e9304c1bae9e5e24',
        publicPath: '*/',
        overwrite: true
      })
    )

    return config
  },
  generateBuildId: () => {
    const buildId = fs.readFileSync(process.cwd() + '/build/BUILD_ID', 'utf8')
    return buildId.trim()
  },
  poweredByHeader: false
})

[dallen4]

@mattdyoung and anyone who may need it, the example repo for configuring source map uploads to Bugsnag during the build and deployment process can be found here. Please feel free to reach out for any clarifications.

[carloscuesta]

But we can try to kindly remind this, since the fix was pushed “15 months ago”. So maybe reopening an issue to remind that this is a pain for some users will help on releasing this to the next version