Hi Ben, We have embedded V8 version 6.7 in our product. We use it to run and debug JavaScript. While debugging scripts is working okay, debugging ES6 modules using the inspector has this one problem. When using Debugger. evaluateOnCallFrame to inspect variables we keep getting an inspector response with reference errors saying the variables are not defined. This is true for all locally declared variables within the current scope in the "mjs" module (I do not see this problem with the imported module, only the importing module).
It seems like symbols are not generated for the importing 'mjs' module. So do we have to do anything special for modules for this to work? I can share my example if and inspector responses if that will help. Thanks, Nupoor On Tuesday, June 23, 2020 at 2:56:50 AM UTC-7, Ben Noordhuis wrote: > > On Mon, Jun 22, 2020 at 8:18 PM Nupoor Kotasthane <nupoo...@gmail.com > <javascript:>> wrote: > > > > Hi all, > > > > Is the V8 inspector equipped to debug ES6 modules? Our product embeds V8 > and and we integrate with the V8 inspector and use it to debug JavaScript. > We have noticed issues when we try to debug ES6 modules with the inspector. > > > > Thanks, > > Nupoor > > We haven't noticed any major issues in Node.js when it comes to > debugging ES modules. Can you go into details? > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-users/5f0a1cd3-cfa3-4b1d-81d4-e569ce83fe7bo%40googlegroups.com.
