Skip to content
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

TypeError: freeParser.getUsageInstance is not a function #23

Open
piotr-cz opened this issue Nov 29, 2022 · 0 comments
Open

TypeError: freeParser.getUsageInstance is not a function #23

piotr-cz opened this issue Nov 29, 2022 · 0 comments

Comments

@piotr-cz
Copy link

piotr-cz commented Nov 29, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant