We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
metacall/install#23
When we execute metacall-deploy with the metacall runtime, it throws a warning like:
! 0x223eb60, 0x7f8c8d873e00 does not exists as a valid command.
metacall-deploy should have been able to parse the argv (--version) and should have returned the version of metacall-deploy.
metacall-deploy is taking some pointers as argv which is not an expected behaviour
metacall npm i -g --prefix=/gnu/lib/some_folder @metacall/deploy
metacall /gnu/lib/.metacall/lib/node_modules/@metacall/deploy/dist/index.js --version
Operating System -> MintOS (Linux)
The text was updated successfully, but these errors were encountered:
@aakritiawasthi thanks for reporting, I have solved this bug in the last commit on my PR: #504
I will merge this into develop and tag a new version as soon as possible.
Sorry, something went wrong.
No branches or pull requests
🐛 Bug Report
metacall/install#23
When we execute metacall-deploy with the metacall runtime, it throws a warning like:
! 0x223eb60, 0x7f8c8d873e00 does not exists as a valid command.
Expected Behavior
metacall-deploy should have been able to parse the argv (--version) and should have returned the version of metacall-deploy.
Current Behavior
metacall-deploy is taking some pointers as argv which is not an expected behaviour
Possible Solution
Steps to Reproduce
metacall npm i -g --prefix=/gnu/lib/some_folder @metacall/deploy
metacall /gnu/lib/.metacall/lib/node_modules/@metacall/deploy/dist/index.js --version
Context (Environment)
Operating System -> MintOS (Linux)
The text was updated successfully, but these errors were encountered: