Package Details: yaak 2025.8.2-2

Git Clone URL: https://aur.archlinux.org/yaak.git (read-only, click to copy)
Package Base: yaak
Description: Fast, offline and Git-friendly API client for HTTP, GraphQL, WebSockets, SSE, and gRPC
Upstream URL: https://yaak.app/
Keywords: api api-client graphql grpc http rest websocket websockets
Licenses: MIT
Conflicts: yaak-app-beta, yaak-appimage, yaak-bin, yaak-git
Provides: yaak-app
Submitter: jonasgeiler
Maintainer: jonasgeiler (SoftExpert)
Last Packager: jonasgeiler
Votes: 1
Popularity: 0.64
First Submitted: 2024-09-13 10:25 (UTC)
Last Updated: 2025-11-07 01:29 (UTC)

Latest Comments

1 2 Next › Last »

jonasgeiler commented on 2025-11-07 01:31 (UTC)

@dallasrevolt The problem should now be fixed thanks to the suggestion from @kstolp

dallasrevolt commented on 2025-10-25 02:35 (UTC)

Hello! I got an error:

[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/dallas/.cache/yay/yaak/src/yaak/src-tauri/yaak-templates
npm error workspace @yaakapp-internal/templates@1.0.0
npm error location /home/dallas/.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

vite v7.0.8 building for production...
Generated route tree in 199ms
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.
✓ 3027 modules transformed.
✗ Build failed in 6.85s
error during build:
Could not resolve "./pkg" from "../src-tauri/yaak-templates/index.ts"
file: /home/dallas/.cache/yay/yaak/src/yaak/src-tauri/yaak-templates/index.ts
    at getRollupError (file:///home/dallas/.cache/yay/yaak/src/yaak/node_modules/rollup/dist/es/shared/parseAst.js:401:41)
    at error (file:///home/dallas/.cache/yay/yaak/src/yaak/node_modules/rollup/dist/es/shared/parseAst.js:397:42)
    at ModuleLoader.handleInvalidResolvedId (file:///home/dallas/.cache/yay/yaak/src/yaak/node_modules/rollup/dist/es/shared/node-entry.js:21430:24)
    at file:///home/dallas/.cache/yay/yaak/src/yaak/node_modules/rollup/dist/es/shared/node-entry.js:21390:26
npm error Lifecycle script `build` failed with error:
npm error code 1
npm error path /home/dallas/.cache/yay/yaak/src/yaak/src-web
npm error workspace @yaakapp/app@1.0.0
npm error location /home/dallas/.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
 -> Failed to install the following packages. Manual intervention is required:
yaak - exit status 4

jonasgeiler commented on 2025-08-22 06:28 (UTC)

@kstolp Thanks for the hint! I'll look into it as soon as I can

kstolp commented on 2025-08-21 20:33 (UTC)

@jonasgeiler It looks like rust-wasm needs to be added to the makedepends in order to build. Otherwise you get an error like the one referenced here.

jonasgeiler commented on 2025-05-20 23:41 (UTC) (edited on 2025-05-21 14:17 (UTC) by jonasgeiler)

LET ME KNOW IF YOU HAVE PROBLEMS WITH THE v2025.2.0 BUILD PROCESS.
I currently get random errors that I have no idea how to fix, although before I did a clean build it ran through without errors, so no idea if there's actually a problem.

Thanks for your help!
~ Jonas

jonasgeiler commented on 2025-02-21 12:47 (UTC) (edited on 2025-02-22 10:11 (UTC) by jonasgeiler)

EDIT: Fixed it! 2025.1.1 is out.

This package is currently on hold while I try to fix the build process. So far no luck, but I'm on it.

melonion commented on 2024-12-14 00:54 (UTC)

Clean build, same error:

thread '<unnamed>' panicked at crates/tauri-cli/src/helpers/app_paths.rs:119:5:
Couldn't recognize the current folder as a Tauri project. It must contain a `tauri.conf.json`, `tauri.conf.json5` or `Tauri.toml` file in any subfolder.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
/home/janek/.local/cache/yay/yaak/PKGBUILD: line 56: 172641 Aborted                 (core dumped) npm run tauri build -- --verbose --bundles deb

jonasgeiler commented on 2024-12-01 04:13 (UTC)

It's possible that the upgrade to 2024.12.1 might require a clean build, since the source repository owner has changed.

melonion commented on 2024-11-30 21:37 (UTC)

Always get this error when trying to build:

thread '<unnamed>' panicked at crates/tauri-cli/src/helpers/app_paths.rs:119:5:
Couldn't recognize the current folder as a Tauri project. It must contain a `tauri.conf.json`, `tauri.conf.json5` or `Tauri.toml` file in any subfolder.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

1 2 Next › Last »