-
Notifications
You must be signed in to change notification settings - Fork 30.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose and hook into REPL eval #20531
Comments
Just to make sure I’m understanding this correctly, what you would like is essentially for just running |
@addaleax Yes, that's the idea 👍 Right now it'd kick into the node.js REPL, so it'd be great to hook into that behaviour and wrap evaluation. One thing that would be relevant to the implementation would be support for chaining the evaluations, so the current "default" might need to be exposed somehow like |
There has not been no further traction since opening the PR. Therefore I am going to close this as it is not foreseeable that we implement anything like it soon. Please reopen / leave a comment if you believe this should stay open. |
While building the REPL for https://github.com/TypeStrong/ts-node, I'd love to be able to push people toward using
node -r ts-node/register
for any advanced node.js usage and the one remaining feature to support the REPL. Would it make sense to expose the "default" REPL eval for override andcreateInternalRepl
in some way so projects like the babel CLI andts-node
can hook into and replace the default eval and/or replicatecreateInternalRepl
?The text was updated successfully, but these errors were encountered: