You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering about the possibility of adding a --interpreter argument, specifying the absolute path to the interpreter, to allow use of, say, ts-node for executing migrations. In the project I work on that uses rethinkdb, we've been steadily converting to TypeScript, and migrations are one of the last areas where we're stuck with .js.
We might possibly also need to add an --extensions argument.
Does this seem of value?
The text was updated successfully, but these errors were encountered:
I'm wondering about the possibility of adding a
--interpreter
argument, specifying the absolute path to the interpreter, to allow use of, say, ts-node for executing migrations. In the project I work on that uses rethinkdb, we've been steadily converting to TypeScript, and migrations are one of the last areas where we're stuck with .js.We might possibly also need to add an
--extensions
argument.Does this seem of value?
The text was updated successfully, but these errors were encountered: