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
Command 'Vyper: Compile' resulted in an error (command 'vyper.compileContract' not found) #4
Comments
It also gives a source path error, with a leading / I've deleted the extension folder named tintinweb.vscode-vyper-0.0.9 in VScode and also deleted it from my %user_profile%.vscode\extensions folder It seems there are a couple of errors, scenarios below:
[Compiler Exception] TypeError: Cannot read property 'toString' of undefined I can not reproduce this outside of vsCode |
Hey @DataBeast-IT, thanks for reporting this issue. I think the problem is that I am passing the I believe this should be fairly easy to fix. Would you be down to testing the release candidate before I publish it to confirm that this is fixed? |
Sure! How do I do that? ;-) |
- disable mythx trial code - code cleanup
@DataBeast-IT here's a preview: vscode-vyper-0 0 10 vsix
let me know if that fixes your problem. |
I will check it on windows after the weekend, I have no access to that box at the moment. Below is Linux! 2 scenario's:
after uninstalling the 0.0.10 version, deleting it from .vscode/extensions and reinstalling 0.0.9 the compile on save function works again. |
Generic question: When I compile, where does the compiled contract end up? No file is created in any directory. I checked /usr/local/bin where the vyper executable is located. Nothing to be found. |
we take output artifacts from stdout. the vsix I shared with you previously was broken. I've fixed a couple of issues, briefly tested it on windows, and repackaged it. Please try this one @DataBeast-IT: |
we currently dont save these artifacts. the compile step is basically used to detect if there are any compile-time issues with your code. happy to implement that though, shouldn't be a lot of work. |
Ah ok! That makes sense! Thanks for your help! |
fixed in #5 feel free to open a new issue if you want the extension to actually output bytecode somehow. cheers and thanks for testing! |
I'm getting this error when trying to compile a vyper contract in VS Code with the tintinweb vyper extension.
Command 'Vyper: Compile' resulted in an error (command 'vyper.compileContract' not found)
My setup:
Python 3.8.6
Vyper 0.2.5+commit.a0c561c
VS code 1.50
Windows 10
Vyper is in my user path (running windows 10) and can be called directly if I open a terminal.
I installed Vyper through pip install vyper.
[edit]
I don't use a virtual environment, as this is the only python / vyper project I'm doing on the machine
[/edit]
The text was updated successfully, but these errors were encountered: