-
Notifications
You must be signed in to change notification settings - Fork 69
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: Cannot read properties of undefined (reading 'warnIfFlagDeprecated') #528
Comments
Facing the same issue with Node 14 on aws codebuild containers. I tried it with twilio-cli version 5.0 as well and still it gives the same issue. |
Yeah also facing the same issue. Build pipeline was successful in building using twilio-cli 3.4.1 yesterday. Tried the same build again today and got this error. Tried upgrading both flex-plugin and twilio-cli versions, but no success. Seems something has broken upstream, perhaps. |
Same issue here with twilio-cli 5.1.0 |
@endreymarcell-wise I'm unable to reproduce this with a freshly generated oclif cli and the latest oclif/core So I'm assuming that there's something unique about your code base that's causing this. Can you provide any additional details that might help me reproduce it? Thanks! |
@bmcgrogan here's the dependency on oclif: As you can see, @twilio/cli-core depends on @oclif/core and since it's using ^ as the specifier, it'll get new minor versions as they roll out. So rolling back twilio-cli itself can not help. FWIW my current workaround is to just remove the offending line from this one file on github: echo 'Removing a breaking line from this dependency until https://github.com/oclif/core/issues/528 is fixed'
mv ~/.twilio-cli/node_modules/\@oclif/core/lib/command.js /tmp/command.js.bak
grep -v 'this.warnIfFlagDeprecated' /tmp/command.js.bak > ~/.twilio-cli/node_modules/\@oclif/core/lib/command.js |
Hey @mdonnalley, thanks for picking this up! I'm not sure what would be special about my codebase, and as you can see, others are also reporting the same issue. |
@mdonnalley, this might help: the issue somehow is prominent in Windows machines and Mac Silicon chips. I somehow couldn't reporduce it in my darwin os. |
I am reproducing it on Ubuntu via Github Actions. |
@endreymarcell-wise thanks - any additional details would be greatly appreciated I just tried the following:
And didn't see the issue. Is there a particular command of yours that this is happening on? I also verified that the 1.19.0 is being used throughout the dependency tree:
|
The exact command I am running is |
Thanks for the context - I was able to reproduce it with the following:
I'll report back once I know more about what's causing this |
@endreymarcell-wise The issue is that you're passing the Changing Not binding |
Thanks for pinpointing the issue! |
I'll get in touch with the respective team internally at Twilio. Thanks @mdonnalley ! |
@endreymarcell-wise @shrutiburman happy to help. I'm going to close this issue for now but feel free to reopen it if you feel it's necessary |
Folks following this thread, plugin-flex has released a patch with the fix, v6.0.2, that should solve this problem. |
Describe the bug
I am running oclif as a dependency of twilio-cli (specifically, twilio-cli-core). When trying to run commands using the
twilio
command line tool, I get the following error:The exact context of the exception is this:
This looks like it could have been introduced by #527 (1.19.0)
Our job was still passing 21 hours ago; the PR linked was merged 16 hours ago; our first job today was 3 hours ago and it already failed.
My computer still @oclif/core v1.16.7 locally, and it seems to work without problems.
To Reproduce
Steps to reproduce the behavior:
npm install -g twilio-cli
twilio plugins:install @twilio-labs/plugin-flex
twilio profiles:create
I understand it would be more useful to provide a direct reproduction which only relies on oclif, but if there's indeed an error in the code, it can hopefully be identified by the stack trace.
Expected behavior
Commands run successfully.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: