1- import path from 'node:path'
2- import { fileURLToPath } from 'node:url'
1+ // import path from 'node:path'
2+ // import { fileURLToPath } from 'node:url'
33
4- import bundleAnalyzer from '@next/bundle-analyzer'
5-
6- const withBundleAnalyzer = bundleAnalyzer ( {
7- // eslint-disable-next-line no-process-env
8- enabled : process . env . ANALYZE === 'true'
9- } )
10-
11- export default withBundleAnalyzer ( {
4+ export default {
125 staticPageGenerationTimeout : 300 ,
136 images : {
147 remotePatterns : [
@@ -24,19 +17,19 @@ export default withBundleAnalyzer({
2417 contentSecurityPolicy : "default-src 'self'; script-src 'none'; sandbox;"
2518 } ,
2619
27- webpack : ( config ) => {
28- // Workaround for ensuring that `react` and `react-dom` resolve correctly
29- // when using a locally-linked version of `react-notion-x`.
30- // @see https://github.com/vercel/next.js/issues/50391
31- const dirname = path . dirname ( fileURLToPath ( import . meta. url ) )
32- config . resolve . alias . react = path . resolve ( dirname , 'node_modules/react' )
33- config . resolve . alias [ 'react-dom' ] = path . resolve (
34- dirname ,
35- 'node_modules/react-dom'
36- )
37- return config
38- } ,
20+ // webpack: (config) => {
21+ // // Workaround for ensuring that `react` and `react-dom` resolve correctly
22+ // // when using a locally-linked version of `react-notion-x`.
23+ // // @see https://github.com/vercel/next.js/issues/50391
24+ // const dirname = path.dirname(fileURLToPath(import.meta.url))
25+ // config.resolve.alias.react = path.resolve(dirname, 'node_modules/react')
26+ // config.resolve.alias['react-dom'] = path.resolve(
27+ // dirname,
28+ // 'node_modules/react-dom'
29+ // )
30+ // return config
31+ // },
3932
4033 // See https://react-tweet.vercel.app/next#troubleshooting
4134 transpilePackages : [ 'react-tweet' ]
42- } )
35+ }
0 commit comments