1700600 - browserify generated web site, can not inspect variable values, works in Chrome

Status: RESOLVED INVALID

(DevTools :: Debugger, defect, P3)

Description

[tc]

Attachment: Breaking in FireFox

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:86.0) Gecko/20100101 Firefox/86.0

Steps to reproduce:

We're using what I'm fairly sure is the standard way to bundle Angular 1.x apps using Browserify under Gulp:

var files = await glob( paths.scripts );
var b = browserify({
    entries: files,
    debug: true,
    transform: [ngAnnotate]
});

return b.bundle()
    .pipe(source('app.min.js'))
    .pipe(buffer())
    //.pipe(cachebust.resources())  TODO should then take name, add/replace to index.html instead of cacehBustTask
    .pipe(sourcemaps.init({loadMaps: true}))
    .pipe(uglify())
    .on('error', log.error)
    .pipe(sourcemaps.write('./'))
    .pipe(gulp.dest(paths.output));

Actual results:

Can set break points, but inspection of all values always undefined.

Works fine in Chrome

Expected results:

Can set break points, but inspection of all values shows actual values.

Works fine in Chrome and FireFox

Comment 1

[tc]

Attachment: Exact same build working in Chrome

Comment 2

[tc]

v86.0.1 arrived today, and no change

Comment 3

[tc]

Here is a minimal test case : https://github.com/tomchiverton/bugzilla-1700600

Clone it, run "npm install" and then "npm run serve"

Open the given URL.

Observe the log message.

Use CTRL-P to open app.js in the debugger and set a break point on the console.log line (line number 10).

Press F5 to refresh.

FireFox stops on line 10.

Hover over "$state" at end of line 8. Shows as undefined.

Do the same steps in Chromium, shows as a complicated object.

Comment 4

[Hubert Boma Manilla (:bomsy)]

Thanks for reporting and the test case.
I can reproduce it.

Comment 5

[tc]

Still breaks in FF89.

How can we get traction on this ?

Comment 7

[tc]

Still broken in v102

Comment 8

[Hubert Boma Manilla (:bomsy)]

Attachment: Screenshot 2023-06-30 at 15.15.55.png

Finally got some chance to look into this
This relates to map scopes been switched off. Once switched on it works (as shown in attached screenshot)
Also see https://bugzilla.mozilla.org/show_bug.cgi?id=1680228#c3
We are looking into turning map scopes on by default in Bug 1695621.

Comment 9

[Hubert Boma Manilla (:bomsy)]

Closing this for now.