-
-
Notifications
You must be signed in to change notification settings - Fork 37.2k
REPL: import statement inside the Node.js REPL #48084
Copy link
Copy link
Closed as not planned
Labels
feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.replIssues and PRs related to the REPL subsystem.Issues and PRs related to the REPL subsystem.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
Description
Activity
Metadata
Metadata
Assignees
Labels
feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.replIssues and PRs related to the REPL subsystem.Issues and PRs related to the REPL subsystem.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
What is the problem this feature will solve?
Allow
importstatements in REPLWhat is the feature you are proposing to solve the problem?
Instead of:
Can we convert them to dynamic import and execute? Just in the REPL.
Like how top level await was supported in Chrome before TLA was an accepted TC39 proposal.
What alternatives have you considered?
At the least we change the message.
from:
to: