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
{{ message }}
This repository has been archived by the owner on Aug 19, 2024. It is now read-only.
First of all, command outputs are not written to screen.
I've added console.log(error)here to so cli shows what I'm doing wrong and now for commands that use instance connections (instance info, instance list) output is:
TypeError: freeParser.getUsageInstance is not a function
at Options.list (C:\Users\xxx\AppData\Roaming\npm\node_modules\@directus\cli\dist\core\options.js:64:34)
at Help.getCommandHelp (C:\Users\xxx\AppData\Roaming\npm\node_modules\@directus\cli\dist\core\help.js:168:35)
at Command.run (C:\Users\xxx\AppData\Roaming\npm\node_modules\@directus\cli\dist\core\command.js:75:39)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
I've looked up references to this function and indeed it seems that it's not defined anywhere in the package
node 16.18.0
os: windows
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
First of all, command outputs are not written to screen.
I've added
console.log(error)
here to so cli shows what I'm doing wrong and now for commands that use instance connections (instance info, instance list) output is:I've looked up references to this function and indeed it seems that it's not defined anywhere in the package
node 16.18.0
os: windows
The text was updated successfully, but these errors were encountered: