Question

122

How to add JS source map into Chrome devtools?

rated 0 times [ 125] [ 3] / answers: 1 / hits: 16424 / 8 Years ago, thu, september 29, 2016, 12:00:00

My deployed JavaScript application raises an exception. The Javascript code is obfuscated. I would like to know, which line in original source code raises an exception. Source maps are not deployed, so Chrome Devtools can't connect them. I may have source maps on my localhost.

So basically I would like to add source maps from my machine to the browser in order to know the line number, where exceptions occurs.

I tried Add Folder to Workspace and Map to File System Resource. It does not help. An exception is visible in browser's console, but it still points into obfuscated javascript source and desired line number is not detectable.

I may do something wrong. Any help is appreciated (including additional extension or other browser usage).

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

tatyanna

Add To Favorites

Follow

Total Points: 552

Total Questions: 96

Total Answers: 96

Location: Cook Islands

Member since Thu, May 21, 2020

4 Years ago

tatyanna questions

1 Failed to load resource: the server responded with 404

Sun, Oct 23, 22, 00:00, 2 Years ago

1 Enable/disable submit button with react-hook-form in onBlur mode

Wed, Apr 7, 21, 00:00, 3 Years ago

1 How can I reset form after submit in reactjs hooks

Tue, Jul 14, 20, 00:00, 4 Years ago

1 Nest can't resolve dependencies of the UserModel (?)

Sun, Nov 17, 19, 00:00, 5 Years ago

1 How to add an Event Listener on elements that are not yet in the DOM [no-jQuery]?

Sun, Sep 1, 19, 00:00, 5 Years ago

View All

answered 8 Years ago dannyc · Accepted Answer

As powerful as Workspaces are, there are some limitations you should be aware of.

Limitations

Only style changes in the Elements panel are persisted; changes to the DOM are not persisted.

Only styles defined in an external CSS file can be saved. Changes to element.style or to inline styles are not persisted. (If you have inline styles, they can be changed on the Sources panel.)

Style changes in the Elements panel are persisted immediately without an explicit save -- Ctrl + S or Cmd + S (Mac) -- if you have the CSS resource mapped to a local file.

If you are mapping files from a remote server instead of a local server, when you refresh the page, Chrome reloads the page from the remote server. Your changes still persist to disk and are reapplied if you continue editing in Workspaces.

You must use the full path to a mapped file in the browser. Even your index files must include .html in the URL, in order to see the staged version.

https://developers.google.com/web/tools/setup/setup-workflow