Skip to content
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

Dealing with .map file #6

Open
guiihlopes opened this issue Jul 10, 2020 · 3 comments
Open

Dealing with .map file #6

guiihlopes opened this issue Jul 10, 2020 · 3 comments

Comments

@guiihlopes
Copy link

Hey Thibault,

how do you deal with .map generated file in the build process?

When we tokenize our environments and then replace, we are manipulating the builded bundle and we are moving the columns in minified files. In this way our .map file is useless for error tracking systems like Sentry.io which uses .map files to tell us which line in the source files that generated error.

Thanks for advance!

@MattBevis
Copy link

@guiihlopes did you manage to solve this issue?

@guiihlopes
Copy link
Author

@guiihlopes did you manage to solve this issue?

Hey @MattBevis! No, I didn't solve this issue yet... :(

@Thibaultce
Copy link
Owner

@guiihlopes I don't have a solution for that.
I used this approach only for a small project where we did not care about the .amp files. Sorry 🙁

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

No branches or pull requests

3 participants