include source maps for JS

RESOLVED FIXED

Status

P3
normal
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: kngo, Assigned: kngo)

Tracking

x86
macOS

Details

(Whiteboard: [repoman])

(Assignee)

Description

4 years ago
When building JS and CSS for anything except prod, configure the build system to include source maps for easier debugging.
(Assignee)

Updated

4 years ago
Assignee: nobody → kngo
Blocks: 1072695
Why not generate them for prod? They only get downloaded when you open the dev tools right?
(Assignee)

Comment 2

4 years ago
I was mistaken before and thought they were inlined. Yeah, we'll have it for prod too.

Updated

4 years ago
Priority: -- → P4
(Assignee)

Updated

4 years ago
Summary: include source maps for CSS and JS dev/stage builds → include source maps for CSS and JS
(Assignee)

Updated

4 years ago
Blocks: 1084690
(Assignee)

Updated

4 years ago
No longer blocks: 1084690
(Assignee)

Comment 3

4 years ago
Source maps for JS: https://github.com/mozilla/marketplace-gulp/pull/4
Priority: P4 → P3
Whiteboard: [repoman]
(Assignee)

Comment 4

4 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
Last Resolved: 4 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.