Question 197582 in Javascript Question posted in
A very good W3school tutorial can be found here.

Javascript – How can I figure out what variables are called after minification?

When debugging production code in DevTools I might be so lucky that I get a sourcemap to look at when setting up logpoints/breakpoints. This allows me to inspect variables when I have set a breakpoint by hovering over the variables, but that is slow and sometimes I would just like to set up what Chrome calls "logpoints", which are breakpoints that does not stop the program, but that can evalute an expression and print it to the console.

logpoint setup

This is where having a source map stops being useful, as the "mapped variable name" is not available when evaluating the expression later on. In reality, the variable isSubmitting might be called u31a, so I cannot access its value and just get an error about isSubmitting not being defined.

error in console

How can I easily figure out what the underlying "real" variable name is called? This also applies when stopping at a breakpoing and wanting to evalute code in the console. Most of these variables are then also not available using their real name. This applies to imports as well, which usually gets some kind of prefix.

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    The answer was very near. You can ask to see the non-sourcemapped version by clicking the filename seen in the screenshot below (note: "(From EditThresholdValuesForm-0a4d9fb7.js)": enter image description here

    Which gives you the real names: non-source-mapped

    In this case, isSubmitting is mapped to the variable called h


  2. 0

    I had the same problem as you but ended up debugging a build without source maps.

    Besides using source maps you could always build your app without minification and debug without source maps. Note that a non-minified build version is not your source code. This way you could see EXACT code of your build.

    The problem with source maps that combining minification + treeshaking you could end up with non well formed source maps. Just saying… source maps are complicated matter…

    When using Vite for example I can have a build without minification:

    npx vite build --minify=false

    Also since Vite uses Rollup for bundling we need to set Rollup option: treeshake: false.

    In the end I get a very build version that I can debug without source maps and see exact build code after transpiling and bundling that will be deployed.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search