productionBrowserSourceMaps doesn't work with profiler

What version of Next.js are you using?

latest in package.json at time of submission - 10.1.3

What version of Node.js are you using?

14.16.0

What browser are you using?

chrome

What operating system are you using?

macOS

How are you deploying your application?

next build --profile; next start (local in prod mode)

Describe the Bug

Starting with npx create-next-app --example with-typescript with-typescript-app, I added:

module.exports = {
  productionBrowserSourceMaps: true,
}

to next.config.js, and I altered npm run build to run:

    "build": "next build --profile",

Then when I did a build and a start, the React Profiler doesn't show the proper names of the components:

Expected Behavior

In prod mode with --profile and productionSourceMaps, I expect profiler to show proper names of components:

To Reproduce

See above, I used with-typescript and altered two files.

Start with the with-typescript example, next.config.js, and the build script changed to run next build --profile. Reproduce with productionBrowserSourceMaps: true and next start, then inspect the React Profiler output in Chrome. Done means production profiling shows the proper component names, matching the expected screenshot.