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.

Sign up for GitHub

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

Jump to bottom

sourcemap for production builds is useless #24241

Closed
richvdh opened this issue Jan 16, 2023 · 0 comments · Fixed by #28499
Closed

sourcemap for production builds is useless #24241

richvdh opened this issue Jan 16, 2023 · 0 comments · Fixed by #28499
Assignees
@t3chguy
Labels
A-Developer-Experience T-Task Tasks for the team like planning

Comments

@richvdh
Copy link
Member

richvdh commented Jan 16, 2023

The sourcemap for app and staging (for example, https://staging.element.io/bundles/51733431847a348f8b7e/init.js.map) is somewhat useless and contains only 2488 mappings - most of them to webpack:///./src/favicon.ts - compared to the same on develop (https://develop.element.io/bundles/1b8575a8c64aae903849/init.js.map, which contains 563564 mappings.

This makes investigating problems on the production builds particularly painful.
@dbkr dbkr added T-Task Tasks for the team like planning A-Developer-Experience labels Jan 16, 2023
@t3chguy t3chguy self-assigned this Nov 20, 2024
@t3chguy t3chguy mentioned this issue Nov 20, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@t3chguy t3chguy

Labels
A-Developer-Experience T-Task Tasks for the team like planning
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix source maps in production builds element-hq/element-web
3 participants
@dbkr @richvdh @t3chguy