REPL with package.json "type":"module"

[dilyanpalauzov]

Just as having "type":"module" in package.json in the current directory implies that .js files can do import x from 'y', typing node (and then some code) in the directory, where that package.json is, shall also understand import x from 'y'.

In addition there shall be a way to pass a command line switch to node, so that on REPL it understands ES6 import.

[BridgeAR]

@dilyanpalauzov ideally it should understand both, no matter if "type": "module" is used or not.

[dilyanpalauzov]

I propose also, that node --input-type=module does not print to stderr Cannot specify --input-type for REPL.

[devsnek]

I'm working on adding static imports and such to V8's repl mode, it won't be contingent on mode flags.

[BridgeAR]

@devsnek do you have the time to look into adding the REPL mode to core as well? This likely needs some work on the VM module and you are probably one of the best to look into that?

[devsnek]

@BridgeAR yeah I can look into it eventually... the main change would probably just be making default eval use Runtime.evaluate

[steeling]

any update on this?

[Olshansk]

🏓

[keeganpoppen]

this would be amazing

[UltiRequiem]

Bump, this would be very cool

[TomasHubelbauer]

For people who landed here from Google and don't need REPL specifically but --eval will do, check out --input-type=module:

node --input-type=module --eval "import test from './test.js'; console.log(test);"

[0xdevalias]

From another related issue:

• REPL: import statement inside the Node.js REPL #48084

Fix for this was implemented and merged at #48129

Originally posted by @hemanth in #48084 (comment)

Looking at that PR:

• repl: display dynamic import version in error message. #48129

Example of the new error that proactively hints how to do it:

> import { diff } from 'node:util';
import { diff } from 'node:util';
^^^^^^

Uncaught:
SyntaxError: Cannot use import statement inside the Node.js REPL, alternatively use dynamic import: const { diff } = await import("node:util");