Cannot profile production build

[sarink]

Since there is currently no way to get source maps on a production build, how are we supposed to profile the application? Profiling in development mode is, obviously, not the same. And if you are in production mode, then you don't get source maps to find where the problem lies.

I know that there is an experimental feature, but is there anything more reliable, or any workaround for an older version of next? I find it hard to believe that nobody has ever had to do this before 🤔

[jamesmosier]

There is a package for that: next-sourcemaps

But that will likely be deprecated after the experimental sourcemaps support is released.

Out of curiosity, why doesn't the experimental feature work for you?

[sarink]

Even with next-sourcemaps, it appears functions/classnames are obfuscated. Is there something else that needs to be done? The experimental feature doesn't work because we're on next 9.3.5 (and it only exists in 9.4+)

[jamesmosier]

which devtool are you using with next-sourcemaps?

[sarink]

devtool: 'source-map',

The source maps are working, that is, I can see a bunch of .map files in the output, however, the code is obfuscated, as if it's still being run through uglify (or whatever next uses)? I haven't found a way to disable that (except of course for running in dev mode, which kind of defeats the purpose)

[Vadorequest]

I have source maps working in production.

You must use "@zeit/next-source-maps": "0.0.4-canary.1", specifically, any other version will fail.

https://github.com/UnlyEd/next-right-now/blob/v2-mst-aptd-gcms-lcz-sty/package.json#L144

And, as stated above, this package will be deprecated soon and they'll be integrated within Next.js itself.

[sarink]

Yes, I am using the canary version of that library. The source maps are working. The problem seems is that with dev: false the code is still obfuscated.

[Vadorequest]

I don't use Next.js through a custom server, but using Serverless mode, so I wouldn't know about that, sorry.