Designating a module as library code

[fatcerberus]

It is possible right now to call JsParse() or JsRun() using the flag JsParseScriptAttributeLibraryCode to designate the script as library code and make it invisible to the debugger. It doesn't appear to be possible to do the same for ES modules.

Can this be done?

[akroshg]

@fatcerberus thanks for reporting this.
@liminzhu @suwc this should be allowed, right?

[liminzhu]

+@agarwal-sandeep who is familiar with the debugging APIs.

Seems reasonable that we should allow host/debugger to ignore certain modules.

[agarwal-sandeep]

+1 we should allow.

[fatcerberus]

In my case when debugging an ES module-based codebase, the debugger's first stop tends to be one of my runtime modules, rather than the game's root module. So it'd be nice if I could step over those by default.

[dilijev]

We have internal operations we use to do this for Intl.js library code. Maybe we can expose those as JSRT APIs?

[fatcerberus]

We have internal operations we use to do this for Intl.js library code. Maybe we can expose those as JSRT APIs?

As noted above, you can already do this with normal scripts, using the parse flag JsParseScriptAttributeLibraryCode. It's just that there's no equivalent option for ES modules.