import.meta.url showing an extension path not the script path

I’ve reproduced on the latest version of NW.js and I’ve searched for import.meta.url to no results.

I am not sure if this is technically possible with how NW.js works, but currently import.meta.url prints a path into a web extension as opposed to a file system path of the script. If this is possible to be somehow intercepted and converted to the file system path, that would be very useful as it would provide an ESM-canonical way of figuring out the current script’s path on the file system. Thank you

NWJS Version : nwjs-sdk-v0.54.1-osx-x64 Operating System : macOS

Expected behavior

import.meta.url should return a file:/// path.

Actual behavior

import.meta.url returns chrome-extension://dicgdfmjdcflpdchdnbjfppblikeeofl/index.js.

How to reproduce

• Download the latest SDK
• Copy it to a new folder
• Create index.html referencing index.js and package.json with index.html for main
• Add this to index.js:

  window.addEventListener('load', () => {
    document.body.append(import.meta.url);
  });
  

• Run nwjs-sdk-v0.54.1-osx-x64/nwjs.app/Contents/MacOS/nwjs .
• See the incorrect path printed:

[frank-dspeed]

@TomasHubelbauer the chrome app and extension url is what enables the whole chrome apps and extension api support in your main background Page.

You get access to all internal API’s like Screen and so on. You can Modify any URL and so on for example you can even disable cors via that as you can intercept requests and modify headers.

[TomasHubelbauer]

I see. I also tried __dirname and __filename to see if they maybe are injected into the browser context like require is, but they do not seem to be. Just putting this out here if anyone finds it useful in the future.