Skip to content

Private source maps support #173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mb2140 opened this issue Aug 26, 2016 · 6 comments
Open

Private source maps support #173

mb2140 opened this issue Aug 26, 2016 · 6 comments

Comments

@mb2140
Copy link

mb2140 commented Aug 26, 2016

I'm trying to think through an approach for using private SourceMaps with stacktracejs. Since the error logger runs on the client, it needs to parse the SourceMap for accurate information - correct? Is it even possible to do this privately?

@RyanHow
Copy link

RyanHow commented Sep 6, 2016

I can't see why you couldn't capture the stack trace of the minified version, send it to the developer. Then the developer then opens a page. You can paste the minified stack trace in and it can convert it back into a stack trace, then run the source map over it (which is available to the developer). Not sure how to convert the stack trace to JSON then back again though? Still would be not very automated.

Ideally, I'd like the minified stack trace sent to a server, which then can do the source mapping.

@kirylkastko
Copy link

I would love to have this feature too. I want to have obfuscated code and clear log message in the same time. Please let me know if I can help somehow.

@pranaymohan
Copy link

Any update/progress on this? Being able to use stacktrace-gps with private source maps would be great!

@eriwen
Copy link
Member

eriwen commented Dec 12, 2016

I'm trying to think of the best way to solve this. It seems like the only really secure way is to have a node-based tool that loads source maps from the local filesystem. The problem with hosting source maps on the web in a "secret" location (the way Errorception does this) is that the URL is plain text and so is exposed in ways that passwords are not.

It would take me a while to find enough time to develop a separate tool for this unless it's easy or I have community help.

Maybe there's another clever way to handle this, or someone wants to provide a design specification that would help us all get it solved.

@eriwen eriwen added this to the 2.0 milestone Dec 18, 2016
@eriwen eriwen changed the title Private source maps? Private source maps support Dec 18, 2016
@maxbaluev
Copy link

any updates?

@nishantjoshtech
Copy link

nishantjoshtech commented Mar 9, 2022

Hi @eriwen, Any updates on the feature request?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

7 participants