fabcar-blockchain-sample icon indicating copy to clipboard operation
fabcar-blockchain-sample copied to clipboard

Step 2: Choose IBM Blockchain Platform: Package a Smart Contract Project continues to throw error message

Open Github4Aaron opened this issue 5 years ago • 5 comments

When completing Step 2 of the tutorial ("Package the Smart Contract") and after navigating to the Contract folder as the root, when one attempts to select the "IBM Blockchain Platform: Package a Smart Contract Package", and error is thrown that reads:

"Failed to determine workspace language type, supported languages are JavaScript, TypeScript, Go and Java. Please ensure your contract's root-level directory is open in the Explorer."

@ljbennett62

Github4Aaron avatar Jul 26 '19 16:07 Github4Aaron

@Github4Aaron this error often happens if you have other directories open in your VSCode instance. Please try and open a new VSCode instance, with only the Contract directory. See if that fixes the problem.

horeaporutiu avatar Jul 30 '19 19:07 horeaporutiu

I also get the same error after running that. below is the output of the terminal

Executing task: npm run build <

[email protected] build /home/fabric/fabcar-blockchain-sample/web-app/client ng build

sh: 1: ng: not found npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn npm ERR! [email protected] build: ng build npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the [email protected] build script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! A complete log of this run can be found in: npm ERR! /home/izackk/.npm/_logs/2019-08-22T12_58_13_443Z-debug.log The terminal process terminated with exit code: 1

Terminal will be reused by tasks, press any key to close it.

16isaac89 avatar Aug 22 '19 13:08 16isaac89

This "@Github4Aaron this error often happens if you have other directories open in your VSCode instance. Please try and open a new VSCode instance, with only the Contract directory. See if that fixes the problem." this worked for me

16isaac89 avatar Aug 22 '19 13:08 16isaac89

@Github4Aaron were you able to resolve this?

sandhya-nayak avatar Jan 18 '20 02:01 sandhya-nayak

This "@Github4Aaron this error often happens if you have other directories open in your VSCode instance. Please try and open a new VSCode instance, with only the Contract directory. See if that fixes the problem." this worked for me

nope it does not work for me

veasnasous2 avatar Feb 05 '20 23:02 veasnasous2