Package Details: yaak 2025.1.2-1

Git Clone URL: https://aur.archlinux.org/yaak.git (read-only, click to copy)
Package Base: yaak
Description: 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-02-26 16:55 (UTC)

Latest Comments

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

jonasgeiler commented on 2024-11-18 03:06 (UTC)

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

SoftExpert commented on 2024-09-16 18:33 (UTC) (edited on 2024-09-17 08:58 (UTC) by SoftExpert)

Hello Jonas,

Cheers from your future co-maintainter, if you want !