Cameron Nursall

Ya it works fine when I am just running `npm run dev`, but is broken after a build. So it is something about the build process in 13.5 that is...

I tracked it down to a specific commit that broke it. https://github.com/vercel/next.js/commit/83c18deafe4f133f74ef2b1e0512228098d48cba It has something to do with the SWC minifier. If you set `keep_fnames` to `false` in `packages/next/src/build/webpack/plugins/terser-webpack-plugin/src/index.ts` then...

I think it is because they changed the defaults for the SWC minifier in 13.5.4, from the default of `keep_fnames: false` to `keep_fnames: true`. I'm honestly not sure why this...

@lutfi-haslab Not in anyway that I have noticed in production, since it is still being minified, just using the pre v13 minifier. The only difference I have noticed, or at...

#504

> @ORizzo > > > I was having the same issue, and just upgrade the next.js version to 15.5.5 (latest version) solved my issue. > > which react-paginate version? still...

Seems like we are all having the issue #501 13.5.3 is working fine on a build, so it is something that happened specifically between 13.5.3 and 13.5.4. Tracking it down...

Really hoping this happens sometime in 2023 so I can use the analytics coming out of Vercel in a BI tool. Especially now that GA has become pretty useless with...