-
Notifications
You must be signed in to change notification settings - Fork 157
packaging typescript chaincode fails #2193
Comments
I have the same problem #2020. And when I try to "Package Open Project" I have this error:
|
I have the same problem, when I try to "Package Open Project" a sample go CRUE contract project, I get fail log:
|
[Workaround] Pending the current fix... you can revert to version 1.39 of vscode which works well for me. |
I confirm your workaround @johndacost . It also solves the 'fsPath' problem. |
I could recreate the packaging failing to do anything after compiling the TypeScript, using VS Code 1.44.x. I'm unable to recreate the As @johndacost mentioned, a workaround is to downgrade VS Code to a previous version such as 1.39 - until we figure out what has changed in VS Code and what changes we can make in the extension. |
Signed-off-by: Jake Turner <jaketurner25@live.com>
Signed-off-by: Jake Turner <jaketurner25@live.com>
A fix went in for this in our v1.0.27 release yesterday. As I've been unable to verify the Thanks, |
@Jakeeyturner Hello, I have updated to v1.0.27, and when click the package open project it still occurs the error:
|
My issue seems to be fixed, thanks Jake |
Works fine, Thanks ! |
@Jakeeyturner I am facing the same issue. I have the latest VSC (1.44.2) and IBM Blockchain platform extension (1.0.27). Additional Info: I am trying to create the package using WSL2 with Ubuntu 18.04. Update: After downgrading VSC to version 1.39.2, everything worked as expected. |
The 1.0.27 version doesn't resolve for me the fsPath problem nor the original packaging one. |
Please could you provide some information on your operating system, VS Code version, extension version, contract language and any prompts you clicked, then add it to this issue --> #2243 Thanks. |
@hbksagar when you say you "Additional Info: I am trying to create the package using WSL2 with Ubuntu 18.04." Does that mean you are using remote development in vscode? |
The chaincode is compiled properly, i.e. shows up in the
dist/
directory but not actually packaged. No error are generated.Expected Behavior
Packaged smart contract should show up in the »smart contracts« pane.
Actual Behavior
When using typescript as the language for the chaincode, nothing happens.
When using javascript as the language for the chaincode, the package shows up.
Possible Fix
N/A
Steps to Reproduce
Existing issues
N/A
Log File
Logfiles are error free. Only says
[INFO] packageSmartContract
Your Environment
The text was updated successfully, but these errors were encountered: