New issue
Advanced search Search tips

Issue 781648 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Feature



Sign in to add a comment

Feature Request: Switch or flag to disable JavaScript source maps

Reported by sarahrhg...@gmail.com, Nov 6 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 OPR/48.0.2685.52

Steps to reproduce the problem:
1. Clone a repository with the following:
 a. Uses compiled TypeScript or JSX
 b. Uses Karma and karma-chrome-launcher
e.g. Angular seed project (https://github.com/angular/angular-seed)
2. Install dependencies (npm install)
3. Run tests (npm run test)
4. In the Karma-managed Chrome browser, click Debug
5. Open developer tools
6. Edit developer tool settings
7. Disable JavaScript source maps
8. Close developer tools
9. Reopen developer tools and begin debugging the compiled JavaScript

What is the expected behavior?
Karma allows developers to configure custom launcher settings for karma-chrome-launcher. If I prefer to debug the compiled JavaScript, I would expect a flag (--disable-javascript-source-maps) so I could configure a custom launcher.

What went wrong?
No flag to disable JavaScript source maps, need to open and disable setting and reopen developer tools every time.

Did this work before? No 

Chrome version: 61.0.3163.100  Channel: n/a
OS Version: OS X 10.12.6
Flash Version:
 
Labels: Needs-Milestone
Labels: -Type-Bug -Needs-Milestone Type-Feature
Status: Untriaged (was: Unconfirmed)
sarahrhgrefalda@ Thanks for filling in. Considering this issue as an feature request and marking it as untriaged for further triage from dev team.

Thank You!

Comment 4 by l...@chromium.org, Nov 13 2017

Cc: l...@chromium.org
Labels: Needs-Feedback
Thanks for the report.  This is strange, the "Enable JavaScript Source Maps" setting in the DevTools preferences should be always persisted, even if you close and reopen it.

I'm not super familiar with karma-chrome-launcher, but could you try forcing to reuse the same Chrome profile?  I'm thinking that may allow it to remember your DevTools settings each time.

If it allows custom flags, could you please try adding:
flags: ['--user-data-dir=' + some_custom_folder]

More details on it here: https://chromium.googlesource.com/chromium/src/+/master/docs/user_data_dir.md#overriding-the-user-data-directory
Great question and suggestion. I haven't tried this yet but will in the next week and report back. Thank you.
Status: WontFix (was: Untriaged)

Sign in to add a comment