Home / GitHub Page

Bulild CLI-CLIENTi8

I cannot build the cliclient

Can someone please help me in the same, I have no problem in building the desktop or mobile application

ERROR log

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   'start'
1 verbose cli ]
2 info using npm@6.13.4
3 info using node@v12.16.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle joplin@1.0.161~prestart: joplin@1.0.161
6 info lifecycle joplin@1.0.161~start: joplin@1.0.161
7 verbose lifecycle joplin@1.0.161~start: unsafe-perm in lifecycle true
8 verbose lifecycle joplin@1.0.161~start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\risha\Desktop\joplin\CliClient\node_modules\.bin;C:\Users\risha\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\local\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\risha\bin;C:\Python27;C:\Python27\Scripts;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Program Files\Git\cmd;C:\Program Files\nodejs;C:\ProgramData\chocolatey\bin;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\Java\jdk1.8.0_211\bin;C:\Users\risha\AppData\Local\Microsoft\WindowsApps;C:\Users\risha\AppData\Roaming\npm;C:\Program Files\Git\usr\bin\vendor_perl;C:\Program Files\Git\usr\bin\core_perl
9 verbose lifecycle joplin@1.0.161~start: CWD: C:\Users\risha\Desktop\joplin\CliClient
10 silly lifecycle joplin@1.0.161~start: Args: [
10 silly lifecycle   '/d /s /c',
10 silly lifecycle   "gulp build -L && node 'build/main.js' --profile ~/Temp/TestNotes2 --stack-trace-enabled --log-level debug --env dev"
10 silly lifecycle ]
11 silly lifecycle joplin@1.0.161~start: Returned: code: 1  signal: null
12 info lifecycle joplin@1.0.161~start: Failed to exec start script
13 verbose stack Error: joplin@1.0.161 start: `gulp build -L && node 'build/main.js' --profile ~/Temp/TestNotes2 --stack-trace-enabled --log-level debug --env dev`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:311:20)
13 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:311:20)
13 verbose stack     at maybeClose (internal/child_process.js:1021:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid joplin@1.0.161
15 verbose cwd C:\Users\risha\Desktop\joplin\CliClient
16 verbose Windows_NT 10.0.18363
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v12.16.1
19 verbose npm  v6.13.4
20 error code ELIFECYCLE
21 error errno 1
22 error joplin@1.0.161 start: `gulp build -L && node 'build/main.js' --profile ~/Temp/TestNotes2 --stack-trace-enabled --log-level debug --env dev`
22 error Exit status 1
23 error Failed at the joplin@1.0.161 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Looks like it might be an issue specific to being run on windows, the npm start command is just an alias for

gulp build -L && node 'build/main.js' --profile ~/Temp/TestNotes2 --stack-trace-enabled --log-level debug --env dev

notice how there are single quotes (’) around 'build/main.js' and if you look at your error log, those quotes are included in the file path. Can you try running the command without them? Or using double quotes (") or something.

Also something that would make it easier to receive support. Please do not share a screenshot of an error log, please take the time to copy and past the error into your message (use a markdown code block). This helps others look up errors and subsequently help you. If you feel that you absolutely need the image, include it alongside the copy and pasted error.

1 Like

@rishabh.malhotra try to compile the CliClient in cmd console instead of PowerShell. For the record, the && operator doesn’t work in Powershell and I think there’s another issues that doesn’t allow you to run on it.

Run npm start on cmd console. If doesn’t work, simply run this command and give us the feedback:

gulp build -L && node build/main.js --profile ~/Temp/TestNotes2 --stack-trace-enabled --log-level debug --env dev

1 Like