You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
xschen@xsdeMacBook-Air pdf.js % yarn
yarn install v1.22.19
info No lockfile found.
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] 🔍 Resolving packages...
warning gulp > glob-watcher > chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
warning gulp > glob-watcher > chokidar > fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
warning gulp > glob-watcher > anymatch > micromatch > snapdragon > source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
warning gulp > glob-watcher > anymatch > micromatch > snapdragon > source-map-resolve > resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
warning gulp > glob-watcher > anymatch > micromatch > snapdragon > source-map-resolve > source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
warning gulp > glob-watcher > anymatch > micromatch > snapdragon > source-map-resolve > urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
warning typogr > mkdirp@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.)
warning wintersmith > chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
warning wintersmith > coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
warning wintersmith > highlight.js@9.18.5: Support has ended for 9.x series. Upgrade to @latest
warning wintersmith > npm > libcipm@4.0.8: This module is no longer used. Please see @npmcli/arborist if you would like to build and reify package trees programmatically.
warning wintersmith > npm > request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
warning wintersmith > npm > node-gyp > request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
warning wintersmith > npm > read-package-tree@5.3.1: The functionality that this package provided is now in @npmcli/arborist
warning wintersmith > npm > uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
warning wintersmith > npm > request > uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
warning wintersmith > npm > libnpm > libnpmconfig@1.2.1: This module is not used anymore. npm config is parsed by npm itself and by @npmcli/config
warning wintersmith > npm > request > har-validator@5.1.5: this library is no longer supported
warning wintersmith > npm > npm-registry-fetch > make-fetch-happen > node-fetch-npm@2.0.4: This module is not used anymore, npm uses minipass-fetch for its fetch implementation now
warning wintersmith > pug > pug-code-gen > constantinople > babel-types > babel-runtime > core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended forusage due to the number of issues. Because of the V8 engine whims, feature detectionin old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
[2/4] 🚚 Fetching packages...
[3/4] 🔗 Linking dependencies...
warning " > eslint-plugin-mozilla@2.12.5" has unmet peer dependency "@microsoft/eslint-plugin-sdl@github:mozfreddyb/eslint-plugin-sdl#17b22cd527682108af7a1a4edacf69cb7a9b4a06".
warning " > eslint-plugin-mozilla@2.12.5" has incorrect peer dependency "eslint-plugin-html@^6.0.0".
warning " > eslint-plugin-mozilla@2.12.5" has incorrect peer dependency "eslint-plugin-prettier@^3.0.0".
warning " > eslint-plugin-mozilla@2.12.5" has incorrect peer dependency "prettier@^1.19.1".
[4/4] 🔨 Building fresh packages...
[1/7] ⠠ canvas
[-/7] ⠠ waiting...
[3/7] ⠠ fsevents
[-/7] ⠠ waiting...
error /Users/xschen/projects/pdf.js/node_modules/canvas: Command failed.
Exit code: 1
Command: node-pre-gyp install --fallback-to-build --update-binary
Arguments:
Directory: /Users/xschen/projects/pdf.js/node_modules/canvas
Output:
node-pre-gyp info it worked if it ends with ok
node-pre-gyp info using node-pre-gyp@1.0.10
node-pre-gyp info using node@18.9.1 | darwin | arm64
node-pre-gyp http GET https://github.com/Automattic/node-canvas/releases/download/v2.10.1/canvas-v2.10.1-node-v108-darwin-unknown-arm64.tar.gz
node-pre-gyp http download proxy agent configured using: "http://10.127.3.214:3128"
node-pre-gyp ERR! install response status 404 Not Found on https://github.com/Automattic/node-canvas/releases/download/v2.10.1/canvas-v2.10.1-node-v108-darwin-unknown-arm64.tar.gz
node-pre-gyp WARN Pre-built binaries not installable for canvas@2.10.1 and node@18.9.1 (node-v108 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error response status 404 Not Found on https://github.com/Automattic/node-canvas/releases/download/v2.10.1/canvas-v2.10.1-node-v108-darwin-unknown-arm64.tar.gz
gyp info it worked if it ends with ok
gyp info using node-gyp@5.1.1
gyp info using node@18.9.1 | darwin | arm64
gyp info ok
gyp info it worked if it ends with ok
Environment
Version of node-canvas (^2.9.3)
Environment (node v18.9.1 on Mac OS X 12.6 m2 chip)
The text was updated successfully, but these errors were encountered:
Why not release the arm64 version?
Steps to Reproduce
Environment
The text was updated successfully, but these errors were encountered: