Errors building the Zotero Desktop app

[Iago Giné Vázquez]

Dear developers,

After following all the 6 build steps in https://www.zotero.org/support/dev/client_coding/building_the_desktop_app I get the messages below. What should I do?

Thanks!

Iago

...

[js] chrome/content/zotero/components/virtualized-table.jsx
[js] resource/citeproc_rs_wasm.js
[js] chrome/content/zotero/itemTree.jsx

Error: Error: Command failed: npm run build
npm WARN using --force Recommended protections disabled.
npm WARN skipping integrity check for git dependency ssh://g...@github.com/mozfreddyb/eslint-plugin-sdl.git
npm WARN deprecated mkd...@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated ur...@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resol...@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated chok...@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated mkd...@0.3.5: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated coffee...@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated highli...@9.18.5: Support has ended for 9.x series. Upgrade to @latest
npm WARN deprecated cor...@2.6.9: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
[BABEL] Note: The code generator has deoptimised the styling of /home/user/zotero-client/pdf-worker/pdf.js/external/quickjs/quickjs-eval.js as it exceeds the max of 500KB.
scripts/build-pdfjs: 8: rsync: not found
scripts/build-pdfjs: 9: rsync: not found

    at ChildProcess.exithandler (node:child_process:419:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1091:16)
    at ChildProcess._handle.onexit (node:internal/child_process:302:5) {
  code: 127,
  killed: false,
  signal: null,
  cmd: 'npm run build',
  stdout: '\n' +
    '> pdf-w...@1.0.0 build\n' +
    '> npm run build:pdf.js && npm run build:worker\n' +
    '\n' +
    '\n' +
    '> pdf-w...@1.0.0 build:pdf.js\n' +
    '> sh scripts/build-pdfjs\n' +
    '\n' +
    '\n' +
    'added 1184 packages, and audited 1642 packages in 21s\n' +
    '\n' +
    '151 packages are looking for funding\n' +
    '  run `npm fund` for details\n' +
    '\n' +
    '37 vulnerabilities (12 moderate, 25 high)\n' +
    '\n' +
    'To address issues that do not require attention, run:\n' +
    '  npm audit fix\n' +
    '\n' +
    'To address all issues (including breaking changes), run:\n' +
    '  npm audit fix --force\n' +
    '\n' +
    'Run `npm audit` for details.\n' +
    '[01:32:13] Using gulpfile ~/zotero-client/pdf-worker/pdf.js/gulpfile.js\n' +
    "[01:32:13] Starting 'lib'...\n" +
    "[01:32:13] Starting 'createBuildNumber'...\n" +
    '\n' +
    '### Getting extension build number\n' +
    'Extension build number: 61\n' +
    "[01:32:13] Finished 'createBuildNumber' after 62 ms\n" +
    "[01:32:13] Starting 'scriptingLib'...\n" +
    '\n' +
    '### Building default preferences\n' +
    '[01:32:16] asset pdf.scripting.js 111 KiB [emitted] (name: main)\n' +
    '  \n' +
    'webpack 5.84.1 compiled successfully\n' +
    "[01:32:16] Finished 'scriptingLib' after 3.67 s\n" +
    "[01:32:16] Starting 'createLib'...\n" +
    '[01:32:24] asset pdf.sandbox.js 622 KiB [emitted] [big] (name: main)\n' +
    '  \n' +
    'webpack 5.84.1 compiled successfully\n' +
    "[01:32:36] Finished 'createLib' after 20 s\n" +
    "[01:32:36] Finished 'lib' after 24 s\n",
  stderr: 'npm WARN using --force Recommended protections disabled.\n' +
    'npm WARN skipping integrity check for git dependency ssh://g...@github.com/mozfreddyb/eslint-plugin-sdl.git \n' +
    'npm WARN deprecated mkd...@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)\n' +
    'npm WARN deprecated ur...@0.1.0: Please see https://github.com/lydell/urix#deprecated\n' +
    'npm WARN deprecated resol...@0.2.1: https://github.com/lydell/resolve-url#deprecated\n' +
    'npm WARN deprecated chok...@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.\n' +
    'npm WARN deprecated mkd...@0.3.5: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)\n' +
    'npm WARN deprecated coffee...@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)\n' +
    'npm WARN deprecated highli...@9.18.5: Support has ended for 9.x series. Upgrade to @latest\n' +
    'npm WARN deprecated cor...@2.6.9: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.\n' +
    '[BABEL] Note: The code generator has deoptimised the styling of /home/user/zotero-client/pdf-worker/pdf.js/external/quickjs/quickjs-eval.js as it exceeds the max of 500KB.\n' +
    'scripts/build-pdfjs: 8: rsync: not found\n' +
    'scripts/build-pdfjs: 9: rsync: not found\n'
}

[Dan Stillman]

On 7/27/23 7:51 PM, Iago Giné Vázquez wrote:
> After following all the 6 build steps in
> https://www.zotero.org/support/dev/client_coding/building_the_desktop_app
> I get the messages below. What should I do?
>

> […]

>
> scripts/build-pdfjs: 8: rsync: not found
> scripts/build-pdfjs: 9: rsync: not found

It looks like you maybe don't have rsync installed (or at least in the
path for the build process)?

[Iago]

Thanks Dan. Indeed, I didn't have rsync installed, and now it works. Then, when running the step 4, app/scripts/check_requirements, it does not detect the lack of rsync, since I only got failures with respect to the Zotero distribution system.

Best,

Iago

[Dan Stillman]

On 7/28/23 7:50 AM, Iago wrote:

Thanks Dan. Indeed, I didn't have rsync installed, and now it works. Then, when running the step 4, app/scripts/check_requirements, it does not detect the lack of rsync, since I only got failures with respect to the Zotero distribution system.

I've added rsync to check_requirements.