Installation fails

==> Sources are ready. ==> Making package: yaak 2025.2.2-1 (Thu 22 May 2025 03:17:46 PM CEST) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> WARNING: Using existing $srcdir/ tree ==> Starting build()... npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated npmlog@5.0.1: This package is no longer supported. npm warn deprecated gauge@3.0.2: This package is no longer supported. npm warn deprecated are-we-there-yet@2.0.0: This package is no longer supported. npm warn deprecated eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options. npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead npm warn deprecated @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead

added 1057 packages, and audited 1081 packages in 6s

324 packages are looking for funding run npm fund for details

8 vulnerabilities (5 moderate, 3 high)

To address issues that do not require attention, run: npm audit fix

To address all issues (including breaking changes), run: npm audit fix --force

Run npm audit for details. npm warn deprecated npmlog@5.0.1: This package is no longer supported. npm warn deprecated are-we-there-yet@2.0.0: This package is no longer supported. npm warn deprecated gauge@3.0.2: This package is no longer supported.

added 137 packages, and audited 1087 packages in 5s

324 packages are looking for funding run npm fund for details

8 vulnerabilities (5 moderate, 3 high)

To address issues that do not require attention, run: npm audit fix

To address all issues (including breaking changes), run: npm audit fix --force

Run npm audit for details.

yaak-app@0.0.0 build npm run --workspaces --if-present build

build run-p build:*

build:main esbuild src/index.ts --bundle --platform=node --outfile=../../src-tauri/vendored/plugin-runtime/index.cjs

../../src-tauri/vendored/plugin-runtime/index.cjs 138.6kb

⚡ Done in 4ms

@yaakapp/api@0.5.3 build run-s build:copy-types build:tsc

@yaakapp/api@0.5.3 build:copy-types run-p build:copy-types:*

@yaakapp/api@0.5.3 build:copy-types:next cpy --flat ../../src-tauri/yaak-plugins/bindings/serde_json/*.ts ./src/bindings/serde_json

@yaakapp/api@0.5.3 build:copy-types:root cpy --flat ../../src-tauri/yaak-plugins/bindings/*.ts ./src/bindings

@yaakapp/api@0.5.3 build:tsc tsc

@yaakapp-internal/templates@1.0.0 build wasm-pack build --target bundler

[INFO]: 🎯 Checking for the Wasm target... Error: wasm32-unknown-unknown target not found in sysroot: "/usr"

Used rustc from the following path: "/usr/bin/rustc" It looks like Rustup is not being used. For non-Rustup setups, the wasm32-unknown-unknown target needs to be installed manually. See https://rustwasm.github.io/wasm-pack/book/prerequisites/non-rustup-setups.html on how to do this.

Caused by: wasm32-unknown-unknown target not found in sysroot: "/usr"

Used rustc from the following path: "/usr/bin/rustc" It looks like Rustup is not being used. For non-Rustup setups, the wasm32-unknown-unknown target needs to be installed manually. See https://rustwasm.github.io/wasm-pack/book/prerequisites/non-rustup-setups.html on how to do this.

npm error Lifecycle script build failed with error: npm error code 1 npm error path /home/mart/.cache/yay/yaak/src/yaak/src-tauri/yaak-templates npm error workspace @yaakapp-internal/templates@1.0.0 npm error location /home/mart/.cache/yay/yaak/src/yaak/src-tauri/yaak-templates npm error command failed npm error command sh -c wasm-pack build --target bundler

@yaakapp/app@1.0.0 build vite build

Generating routes... Processed routes in 189ms vite v6.2.7 building for production... transforming...

A PostCSS plugin did not pass the from option to postcss.parse. This may cause imported assets to be incorrectly transformed. If you've recently added a PostCSS plugin that raised this warning, please contact the package author to fix the issue. ✓ 2582 modules transformed. ✗ Build failed in 1.68s error during build: Could not resolve "./pkg" from "../src-tauri/yaak-templates/index.ts" file: /home/mart/.cache/yay/yaak/src/yaak/src-tauri/yaak-templates/index.ts at getRollupError (file:///home/mart/.cache/yay/yaak/src/yaak/node_modules/rollup/dist/es/shared/parseAst.js:397:41) at error (file:///home/mart/.cache/yay/yaak/src/yaak/node_modules/rollup/dist/es/shared/parseAst.js:393:42) at ModuleLoader.handleInvalidResolvedId (file:///home/mart/.cache/yay/yaak/src/yaak/node_modules/rollup/dist/es/shared/node-entry.js:21328:24) at file:///home/mart/.cache/yay/yaak/src/yaak/node_modules/rollup/dist/es/shared/node-entry.js:21288:26 npm error Lifecycle script build failed with error: npm error code 1 npm error path /home/mart/.cache/yay/yaak/src/yaak/src-web npm error workspace @yaakapp/app@1.0.0 npm error location /home/mart/.cache/yay/yaak/src/yaak/src-web npm error command failed npm error command sh -c vite build ==> ERROR: A failure occurred in build(). Aborting... -> error making: yaak-exit status 4