Skip to content

Error tracing on production #9213

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

Closed
talhakazmi opened this issue Jan 15, 2018 · 3 comments
Closed

Error tracing on production #9213

talhakazmi opened this issue Jan 15, 2018 · 3 comments
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent severity3: broken

Comments

@talhakazmi
Copy link

Versions

<!--
Output from: `ng --version`.
@angular/cli: 1.5.2
@angular/material: 5.0.3
@angular-devkit/build-optimizer: 0.0.33
@angular-devkit/core: 0.0.20
@angular-devkit/schematics: 0.0.36
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.8.2
@schematics/angular: 0.1.5
typescript: 2.2.2
webpack: 3.8.1

  Windows (10)
-->

Repro steps

I have applied error tracing on development build which shows proper file and line because of sourcemap files as they do exist on development but when i tried the same code on production built, the file showed up is UglifyJs and couldn't understand the line and code.
i can use --sourcemap flag to get the sourcemap on production but i don't want my users to view sourcemap. is there any way i can get proper file and line of error in production without sourcemap

@talhakazmi
Copy link
Author

I have also tried to generate map iles in production with flag --sourcemap and move them on restricted domain which only i can access but so error produced on my machine shows proper file and line number but on other users it wont show.
but i don't want this i have created an error logging file and want to log error with error trace produced on user end.

@Brocco Brocco added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent severity3: broken labels Jan 15, 2018
@hansl hansl unassigned clydin Feb 6, 2018
@alan-agius4
Copy link
Collaborator

Closing in favor of #12375

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent severity3: broken
Projects
None yet
Development

No branches or pull requests

4 participants