Add ability to suppress `.command`s in REPL

What is the problem this feature will solve?

I'm building a custom shell-like REPL for an application that's written in Javascript. To achieve this, I'm using the REPL module because it's more feature-rich than the readline module (for example, using ctrl+r (and looking through the Node code, I couldn't actually find where this functionality is defined...)). It's also much easier to work with than the readline module.

However, I'm trying to secure the application as best as possible so my users don't fall into holes when trying to execute commands, and so I'm restricting access to the REPL dot commands of .editor, .help, etc. I would also like to take advantage of the .commands in my own eval function so I can also extend the functionality of my REPL too.

Specifically: the problem this feature will solve is to allow .commands through to the eval function. Some guard rails will probably need to be put in place (such as making sure the default eval isn't being used, or writing a warning in the docs).

What is the feature you are proposing to solve the problem?

Add an optional property to the ReplOptions called nativeDotCommands (or whatever fits), and adjust the if statement to account for this property (and likely adjustments to other parts of the codebase)

What alternatives have you considered?

Currently, I'm setting repl.commands = {} to remove all the commands, however of course this is throwing an error from my linter because that property is read-only. I can suppress the error, but that still doesn't allow me to use .commands within my application. So far, this is the best work around I've got (short of rewriting and using the readline module.)

Beginne bei der verlinkten if-Anweisung in lib/repl.js und untersuche die Definition von ReplOptions sowie, wie repl.commands bereitgestellt wird. Verfolge, wie Punktbefehle derzeit verarbeitet werden, und ermittle dann, wie eine optionale Einstellung nativeDotCommands ermöglichen könnte, dass sie ein benutzerdefiniertes eval erreichen, ohne das Standardverhalten zu schwächen. Als erledigt gilt die Aufgabe, wenn benutzerdefinierte REPLs Punktbefehle empfangen können, während die bestehende Standardverarbeitung geschützt bleibt.