Repository navigation
Modules doc direct execution test invalid under "type": "module" #34882
Description
Activity
I believe the pattern to use here is
path.resolve(process.argv[1]) === url.fileURLToPath(import.meta.url). It could be worthwhile discussing this.We did discuss
import.meta.mainpreviously, and that discussion could be reopened to follow Deno here. I'd personally support that.You can also use separate files for your library and cli logic.
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
Trying to emulate the Python
__main__check for testing purposes, I found the description in"Accessing the Main Module" is unhelpful when package.json is set to ES modules mode "type": "module".
Suggesting
if (require.main === module)is unhelpful when bothrequireandmoduleare undefined and node throws errors.I see at "No require, ..." that it says no
requirevariable is created in ESM mode, but it doesn't saymoduledisappears also.I see old issues #21143 and linked #21150 but don't understand if they were asking for
require/modulein ESM mode.The modules doc needs updating to reflect what happens under "type": "module" mode. That text has been left behind by the node.js support for ESM.
If there is elsewhere - or could be - hints as to how to emulate the Python
__main__check that'd be of interest to more than a few people.