You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on sourcemap true support for {N}.
Right you can generate sourcemap but there is no way to use them in a dev env to actually see the source of the error.
On android it is already doable using source-map-support.
For it to work on iOS we would need 2 things:
we need to have a prepareStackTrace support for the Error class like it exists in v8. It is used here in source-map-support to "translate" the stack.
the stack format should be the same as android (also as node and browsers) with at ...
The text was updated successfully, but these errors were encountered:
I am working on sourcemap true support for {N}.
Right you can generate sourcemap but there is no way to use them in a dev env to actually see the source of the error.
On android it is already doable using source-map-support.
For it to work on iOS we would need 2 things:
prepareStackTrace
support for theError
class like it exists in v8. It is used here insource-map-support
to "translate" the stack.at ...
The text was updated successfully, but these errors were encountered: