can bytenode have like sourcemap ability?

i wanna get correct pos from jsc exception,so that i can analyze exception and fix it,thx

this is a exception from jsc

TypeError: undefined is not a function
    at /Users/zimengle/Workspace/bytenode/examples/no-module-flag/script.js:1:62
    at Script.runInThisContext (vm.js:126:20)
    at runBytecode (/Users/zimengle/Workspace/bytenode/index.js:105:17)
    at Object.runBytecodeFile (/Users/zimengle/Workspace/bytenode/index.js:167:10)
    at Object.<anonymous> (/Users/zimengle/Workspace/bytenode/examples/no-module-flag/main.js:5:10)
    at Module._compile (internal/modules/cjs/loader.js:869:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:880:10)
    at Module.load (internal/modules/cjs/loader.js:731:32)
    at Function.Module._load (internal/modules/cjs/loader.js:644:12)
    at Function.Module.runMain (internal/modules/cjs/loader.js:932:10)

this is a exception from js

TypeError: a.like is not a function
    at Object.<anonymous> (/Users/zimengle/Workspace/bytenode/examples/no-module-flag/script.js:6:3)
    at Module._compile (internal/modules/cjs/loader.js:869:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:880:10)
    at Module.load (internal/modules/cjs/loader.js:731:32)
    at Function.Module._load (internal/modules/cjs/loader.js:644:12)
    at Function.Module.runMain (internal/modules/cjs/loader.js:932:10)
    at internal/main/run_main_module.js:17:11

[delewis13]

Thanks for the consideration @OsamaAbbas !

To preface this, i’m a junior developer with not much experience working with source-maps and no real understanding of the mechanics of bytenode, so everything should be taken with a grain of salt!

Could you please elaborate on your use-case?

I currently use webpack to bundle my files and generate source maps. These source maps get uploaded to sentry.io, and subsequently any uncaught errors experienced by users are reported to sentry. With the source maps uploaded, these error reports are accompanied by a useful stack trace & the particular offending line of code, mapped back to src. PFA screenshot [have only included a small portion of the page / stack trace] 😃

First, do we really need this feature?

Well I can only speak from my POV from this, but for me the usage of sentry.io [and whatever similar tools that must exist to help debugging in production] takes precedence over the security offered by bytenode. That said, it’s entirely possible i’m misunderstanding something - i’m just working with these tools for the first time - maybe the sourcemaps aren’t as useful as I anticipate.

Definitely would be good to get the input from others, as I can imagine that it would be a complex undertaking.

What do you think of this approach?

Unfortunately my understanding of sourcemaps & bytenode is not good enough to comment!

[s100]

This is likely a problem in your source JavaScript, not bytenode. Try running the same code but use the source JavaScript file instead of the compiled bytecode file.