Closed
Bug 1078093
Opened 10 years ago
Closed 10 years ago
include source maps for JS
Categories
(Marketplace Graveyard :: Code Quality, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kngo, Assigned: kngo)
References
Details
(Whiteboard: [repoman])
When building JS and CSS for anything except prod, configure the build system to include source maps for easier debugging.
Comment 1•10 years ago
|
||
Why not generate them for prod? They only get downloaded when you open the dev tools right?
Assignee | ||
Comment 2•10 years ago
|
||
I was mistaken before and thought they were inlined. Yeah, we'll have it for prod too.
Updated•10 years ago
|
Priority: -- → P4
Assignee | ||
Updated•10 years ago
|
Summary: include source maps for CSS and JS dev/stage builds → include source maps for CSS and JS
Assignee | ||
Comment 3•10 years ago
|
||
Source maps for JS: https://github.com/mozilla/marketplace-gulp/pull/4
Priority: P4 → P3
Whiteboard: [repoman]
Assignee | ||
Comment 4•10 years ago
|
||
Not going to do CSS for now. Since we cache-bust img URLs, we'd have to manually generate a sourcemap, which seems to be way too much effort. It's pretty easy to back-trace a CSS selector/rule to a file anyways.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Summary: include source maps for CSS and JS → include source maps for JS
You need to log in
before you can comment on or make changes to this bug.
Description
•