| 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: | 0 |
| Popularity: | 0.000000 |
| First Submitted: | 2024-09-13 10:25 (UTC) |
| Last Updated: | 2025-05-28 23:28 (UTC) |
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
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.
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
It's possible that the upgrade to 2024.12.1 might require a clean build, since the source repository owner has changed.
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
It's possible that the upgrade to 2024.12.0 might require a clean build, since the source repository owner has changed.
Hello Jonas,
Cheers from your future co-maintainter, if you want !
Pinned Comments
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