18a9c7e371
* Update `packages/` * Update examples * Update tests * Update bench * Update top level files * Fix build * trigger
25 lines
976 B
JavaScript
25 lines
976 B
JavaScript
const withSourceMaps = require('@zeit/next-source-maps')()
|
|
|
|
module.exports = withSourceMaps({
|
|
webpack: (config, options) => {
|
|
// In `pages/_app.js`, Sentry is imported from @sentry/node. While
|
|
// @sentry/browser will run in a Node.js environment, @sentry/node will use
|
|
// Node.js-only APIs to catch even more unhandled exceptions.
|
|
//
|
|
// This works well when Next.js is SSRing your page on a server with
|
|
// Node.js, but it is not what we want when your client-side bundle is being
|
|
// executed by a browser.
|
|
//
|
|
// Luckily, Next.js will call this webpack function twice, once for the
|
|
// server and once for the client. Read more:
|
|
// https://nextjs.org/docs#customizing-webpack-config
|
|
//
|
|
// So ask Webpack to replace @sentry/node imports with @sentry/browser when
|
|
// building the browser's bundle
|
|
if (!options.isServer) {
|
|
config.resolve.alias['@sentry/node'] = '@sentry/browser'
|
|
}
|
|
|
|
return config
|
|
},
|
|
})
|