[Q/A] Production source map ERR_BLOCKED_BY_CLIENT

[Mis-tian]

What happened?

DevTools cannot load source mapping
plasmo: "^0.61.4",

Version

Latest

What OS are you seeing the problem on?

MACOS v13.1

What browsers are you seeing the problem on?

Chrome

Relevant log output

DevTools could not load the source map: could not load the contents of chrome-extension://omckdemngcceglkdafkanadelahgchad/inline.abd4d23e.js.map: system error: net::ERR_BLOCKED_BY_CLIENT
DevTools could not load the source map: Could not load the contents of chrome-extension://omckdemngcceglkdafkanadelahgchad/main.76d731f8.js.map: System error: net::ERR_BLOCKED_BY_CLIENT

(OPTIONAL) Contact Details

No response

Code of Conduct

• I agree to follow this project's Code of Conduct
• I checked the current issues for duplicate problems.

[louisgv]

Yup, the production sourcemap is only for instrumenting outside of the browser (i.e, when using Sentry or a logging service for example). Otherwise, an extension can only instrument its own inline sourcemap (which is the configured done in dev mode)

[Mis-tian]

It was found that in version 0.58 production packages could be mapped with --source-maps turned on.
Now the latest version how to do。
I'm referring to turning on inline source mapping

[louisgv]

What are the use cases for inline source-mapping in production? I can add it back with a flag

[Mis-tian]

1. Suppose I have dev, test, pre, prod environments. I want to turn on the mapping in other environments besides the official production environment, because the APIs of different environments may cause different problems. (This can be done currently with --tag=xxx)

2, for a certain environment in different operating systems, different models of any version of chrome in the problem directly open mapping remote debugging code, more convenient debugging (I mean only in other devices to reproduce the problem)

[louisgv]

@Mis-tian tracking in #397