Customer experience | Sales, Customer Insights,...

PCF control development setup

(1) Share

Report

Posted on by Marc Villeneuve

Hi Everyone, I've been trying to learn how to develop PCF controls and I've run into a roadblock... I've installed the latest version of Node.js, the latest CLI, Visual Studio Code and .net framework 4.6.2 targeting pack. The issue I am having is that for every tutorial I try, I get the same result... a build failure with code: -4058. I have no clue where to start troubleshooting where the error lies, I look at the logs and cannot figure out how to fix this. Has anyone ever faced this?

I have the same question (0)

All responses (11)

Answers (0)

SamiraM 587 on at

Like (0)

Report

Hi,

I have followed the below article and was able to setup.

debajmecrm.com/.../

At what point you are facing the issue? Please elaborate and share the screenshot.

Regards

Samira

Was this reply helpful? Yes No
Marc Villeneuve 10 on at

Like (0)

Report

I too was able to set up the applications, the issue that I am facing is in building the application:

Here's the log it generates (removed the path to shorten)

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'build'
1 verbose cli ]
2 info using npm@6.14.4
3 info using node@v12.17.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle pcf-project@1.0.0~prebuild: pcf-project@1.0.0
6 info lifecycle pcf-project@1.0.0~build: pcf-project@1.0.0
7 verbose lifecycle pcf-project@1.0.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle pcf-project@1.0.0~build: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;...
9 verbose lifecycle pcf-project@1.0.0~build: CWD: C:\vs_workspace\PCF\CopyToClipboard
10 silly lifecycle pcf-project@1.0.0~build: Args: [ '-c', 'pcf-scripts build' ]
11 info lifecycle pcf-project@1.0.0~build: Failed to exec build script
12 silly lifecycle pcf-project@1.0.0~build: Returned: code: -4058 signal: null
13 info lifecycle pcf-project@1.0.0~build: Failed to exec build script
14 verbose stack Error: pcf-project@1.0.0 build: `pcf-scripts build`
14 verbose stack spawn bash ENOENT
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
14 verbose stack at onErrorNT (internal/child_process.js:469:16)
14 verbose stack at processTicksAndRejections (internal/process/task_queues.js:84:21)
15 verbose pkgid pcf-project@1.0.0
16 verbose cwd C:\vs_workspace\PCF\CopyToClipboard
17 verbose Windows_NT 10.0.17763
18 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
19 verbose node v12.17.0
20 verbose npm v6.14.4
21 error code ELIFECYCLE
22 error syscall spawn bash
23 error file bash
24 error path bash
25 error errno ENOENT
26 error pcf-project@1.0.0 build: `pcf-scripts build`
26 error spawn bash ENOENT
27 error Failed at the pcf-project@1.0.0 build script.
27 error This is probably not a problem with npm. There is likely additional logging output above.
28 verbose exit [ 1, true ]

Was this reply helpful? Yes No
Marc Villeneuve 10 on at

Like (0)

Report

I suspect it it my environment setup.

Was this reply helpful? Yes No
Ana Almeida on at

Like (0)

Report

Hello Marc,

I found a similar situation reported here: stackoverflow.com/.../npm-err-code-elifecycle

Let me know if some of the suggestions works for you.

Was this reply helpful? Yes No
Marc Villeneuve 10 on at

Like (0)

Report

Hi Ana, thanks for your reply, I have tried clearing the cache as the post suggested and this did not work, I have tried deleting all of the generated files and start from scratch and still no luck. I suspect it's a path issue of some sort but I have no way of debugging the scripts to see where exactly it is failing which is quite disheartening.

Was this reply helpful? Yes No
Ana Almeida on at

Like (0)

Report

Hello Marc,

Can you change the location of the PCF C:\vs_workspace\PCF\CopyToClipboard to c:\users\<username>\vs_workspace\PCF\CopyToClipboard?

Was this reply helpful? Yes No
Marc Villeneuve 10 on at

Like (0)

Report

Hi Ana, moved the work space over to my profile but it still didn't work... it was worth a try though.

Was this reply helpful? Yes No
Suggested answer

Marc Villeneuve 10 on at

Like (0)

Report

Hello Ana / Samira, first of all thank you for trying to help. I have sort of found the issue... it's my software installation. I've installed all of the applications on my remote workstation in the office and was able to create a successful build. I guess now my course of action will be to wipe out all of the associated programs on my local pc and try again, if that does not work, at least I have an alternative working environment.

Was this reply helpful? Yes No
Kokulan 18,054 on at

Like (0)

Report

Hi

I had a similar error recently and doing npm install -g sorted my issue.

Thanks

Was this reply helpful? Yes No
Marc Villeneuve 10 on at

Like (0)

Report

Hi Kokulan, thank you for your suggestion I tried npm install -g and still no luck... Yesterday, I re-installed everything yesterday and still the same issue so I suspect it has something to do with my workstation and / or profile on this machine. Like I mentioned, I use another workstation in the office on which I installed all of the required software and it works like a charm so I won't loose any sleep over it.

Cheers!

Was this reply helpful? Yes No