profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/lucasfernog/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Lucas Fernandes Nogueira lucasfernog @tauri-apps Brazil Full Stack Developer

Akryum/guijs 1064

🐣️ The app that makes your #devlife easier.

bernardoaraujor/iota_rspammer 3

Rust-based IOTA 1.5 Client Spammer (Post Chrysalis pt.2)

LInDa-ProPesq/Grupo-5 2

Trabalhos dos alunos do Grupo 5 da disciplina Ciência de Dados

lucasfernog/appbar-snap-behavior 1

Behaviors for the CoordinatorLayout in order to have a snapping AppBarLayout similar to the one used in the GooglePlay app.

Eihen/laratrust 0

Handle roles and permissions in your Laravel application

Jotamucheroni/nucleo-so 0

Núcleo de um sistema operacional para o processador 8086 da Intel, desenvolvido como trabalho para a disciplina de Sistemas Operacioanais II, Unesp - Bauru

lucasfernog/activity-box 0

⚡️📌 Update a pinned gist to contain the latest activity of a user

lucasfernog/advisory-db 0

Security advisory database for Rust crates published through crates.io

lucasfernog/app-extension-dotenv 0

Official Quasar App Extension for dotenv

issue closedtauri-apps/tauri

[docs] Setup for Linux optional dependencies need `squashfs-tools`

On Arch, squashfs-tools should need to add to optional dependencies for AppImage bundle:

thread 'main' panicked at 'mksquashfs is not installed. Please install squashfs-tools and try again.: Os { code: 2, kind: NotFound, message: "No such file or directory" }', /home/runner/work/binary-releases/binary-releases/tooling/bundler/src/bundle/linux/appimage.rs:29:6
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

closed time in 7 hours

mlouielu

issue commenttauri-apps/tauri

[docs] Setup for Linux optional dependencies need `squashfs-tools`

Please reopen if it still happens on @tauri-apps/cli v1.0.0-beta.10 or tauri-cli (Rust CLI) v1.0.0-beta.7.

mlouielu

comment created time in 7 hours

issue commenttauri-apps/tauri

[docs] Setup for Linux optional dependencies need `squashfs-tools`

What's the output of tauri info? We dropped the mksquashfs requirement recently.

mlouielu

comment created time in 7 hours

delete branch tauri-apps/tauri

delete branch : feat/cli.js-cjs

delete time in 7 hours

push eventtauri-apps/tauri

Lucas Fernandes Nogueira

commit sha 205b0dc8f30bf70902979a2c0a08c8bc8c8e5360

feat(cli.js): add CommonJS dist files (#2646)

view details

push time in 7 hours

PR merged tauri-apps/tauri

feat(cli.js): add CommonJS dist files

<!-- Please make sure to read the Pull Request Guidelines: https://github.com/tauri-apps/tauri/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

What kind of change does this PR introduce? (check at least one) <!-- If you are introducing a new binding, you must reference an issue where this binding has been proposed, discussed and approved by the maintainers. -->

  • [ ] Bugfix
  • [x] Feature
  • [ ] Docs
  • [ ] New Binding Issue #___
  • [ ] Code style update
  • [ ] Refactor
  • [ ] Build-related changes
  • [ ] Other, please describe:

Does this PR introduce a breaking change? (check one) <!-- If yes, please describe the impact and migration path for existing applications in an attached issue. Filing a PR with breaking changes that has not been discussed and approved by the maintainers in an issue will be immediately closed. -->

  • [ ] Yes. Issue #___
  • [ ] No

The PR fulfills these requirements:

  • [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
  • [x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

  • [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

+22 -7

0 comment

2 changed files

lucasfernog

pr closed time in 7 hours

delete branch tauri-apps/tauri

delete branch : fix/api-ts-output

delete time in 7 hours

push eventtauri-apps/tauri

Lucas Fernandes Nogueira

commit sha 0f321ac08d56412edd5bc9d166201fbc95d887d8

fix(api): do not ship TS files, closes #2598 (#2645)

view details

push time in 7 hours

issue closedtauri-apps/tauri

Tauri npm packages contain .ts files

Describe the bug

When importing @tauri-apps/api, I get TypeScript errors/warnings/hints from inside node_modules.

I thought this was an issue with svelte-check, but as explained in https://github.com/sveltejs/language-tools/issues/1056#issuecomment-917918017 this happens because .ts files are being imported from node_modules.

This might also be the cause of https://github.com/tauri-apps/tauri/issues/2594

Platform and Versions

<details> <summary>Details</summary>

Operating System - Mac OS, version 10.15.7 X64

Node.js environment
  Node.js - 14.16.0
  @tauri-apps/cli - 1.0.0-beta.10
  @tauri-apps/api - 1.0.0-beta.8

Global packages
  npm - 6.14.11
  yarn - 1.22.10

Rust environment
  rustc - 1.54.0
  cargo - 1.54.0

App directory structure
/node_modules
/src-tauri
/build
/.git
/src

App
  tauri.rs - 1.0.0-beta.8
  build-type - bundle
  CSP - default-src blob: data: filesystem: ws: wss: http: https: tauri: 'unsafe-eval' 'unsafe-inline' 'self' img-src: 'self'
  distDir - ../build
  devPath - http://localhost:5000
  framework - Svelte

</details>

Stack Trace

<details> <summary>Details</summary>

> @ check /Users/kasper/dev/git/kryp
> svelte-check --tsconfig ./tsconfig.json


====================================
Loading svelte-check in workspace: /Users/kasper/dev/git/kryp
Getting Svelte diagnostics...

/Users/kasper/dev/git/kryp/node_modules/@tauri-apps/api/helpers/event.ts:7:1
Error: This import is never used as a value and must use 'import type' because 'importsNotUsedAsValues' is set to 'error'. 

import { WindowLabel } from '../window'
import { invokeTauriCommand } from './tauri'


/Users/kasper/dev/git/kryp/node_modules/@tauri-apps/api/event.ts:15:1
Error: This import is never used as a value and must use 'import type' because 'importsNotUsedAsValues' is set to 'error'. 
import { transformCallback } from './tauri'
import { LiteralUnion } from 'type-fest'



/Users/kasper/dev/git/kryp/node_modules/@tauri-apps/api/helpers/os-check.ts:8:20
Hint: 'appVersion' is deprecated. 
function isLinux(): boolean {
  return navigator.appVersion.includes('Linux')
}


/Users/kasper/dev/git/kryp/node_modules/@tauri-apps/api/helpers/os-check.ts:12:20
Hint: 'appVersion' is deprecated. 
function isWindows(): boolean {
  return navigator.appVersion.includes('Win')
}


/Users/kasper/dev/git/kryp/node_modules/@tauri-apps/api/helpers/os-check.ts:16:20
Hint: 'appVersion' is deprecated. 
function isMacOS(): boolean {
  return navigator.appVersion.includes('Mac')
}


/Users/kasper/dev/git/kryp/src/lib/NumericInput.svelte:36:9
Error: Object is possibly 'null'. (ts)
      } else {
        start -= 1
        end -= 1


/Users/kasper/dev/git/kryp/src/lib/NumericInput.svelte:37:9
Error: Object is possibly 'null'. (ts)
        start -= 1
        end -= 1
      }


====================================

</details>

closed time in 7 hours

probablykasper

PR merged tauri-apps/tauri

fix(api): do not ship TS files, closes #2598

<!-- Please make sure to read the Pull Request Guidelines: https://github.com/tauri-apps/tauri/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

What kind of change does this PR introduce? (check at least one) <!-- If you are introducing a new binding, you must reference an issue where this binding has been proposed, discussed and approved by the maintainers. -->

  • [x] Bugfix
  • [ ] Feature
  • [ ] Docs
  • [ ] New Binding Issue #___
  • [ ] Code style update
  • [ ] Refactor
  • [ ] Build-related changes
  • [ ] Other, please describe:

Does this PR introduce a breaking change? (check one) <!-- If yes, please describe the impact and migration path for existing applications in an attached issue. Filing a PR with breaking changes that has not been discussed and approved by the maintainers in an issue will be immediately closed. -->

  • [ ] Yes. Issue #___
  • [ ] No

The PR fulfills these requirements:

  • [x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
  • [x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

  • [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

+6 -29

0 comment

4 changed files

lucasfernog

pr closed time in 7 hours

delete branch tauri-apps/tauri

delete branch : fix/workspace-detection

delete time in 8 hours

push eventtauri-apps/tauri

Lucas Fernandes Nogueira

commit sha 8d630bc8c494cba6ac1604b7777b89b763044471

fix(cli.rs): fix workspace detection, fixes #2614, closes #2515 (#2644)

view details

push time in 8 hours

issue closedtauri-apps/tauri

Add more verbose logging when tauri fails to parse a Cargo.toml in a parent workspace

Is your feature request related to a problem? Please describe. Split from #2508. I had to pull the tauri source and debug re.cli in order to determine why my build was failing. If there logging was a bit more verbose, the problem with my project files might have been made clear without ever touching the rs.cli code.

Error currently looks like:

Error: failed to rename `/Users/edgex004/Code/test-tauri-app/src-tauri/target/release/app` to `/Users/edgex004/Code/test-tauri-app/src-tauri/target/release/test-tauri-app`

Caused by:
    No such file or directory (os error 2)

Describe the solution you'd like Adding a warning printout to cli.rs for when get_workspace_dir finds a Cargo.toml in a parent directory, but fails to parse it for some reason. Print the parser error context here.

I have done this on a branch. Error now looks like:

[tauri:build] Found `/Users/edgex004/Code/test-tauri-app`, which may define a parent workspace, but failed to parse it. If this is indeed a parent workspace, undefined behavior may occur: 
    failed to parse Cargo.toml: missing field `description` for key `package` at line 18 column 1
Error: failed to rename `/Users/edgex004/Code/test-tauri-app/src-tauri/target/release/app` to `/Users/edgex004/Code/test-tauri-app/src-tauri/target/release/test-tauri-app`

Caused by:
    No such file or directory (os error 2)

Describe alternatives you've considered Alternatives I thought of are:

  • to error out in this case instead.
  • make the Cargo.toml parser more lax.

Additional context None

closed time in 8 hours

edgex004

issue closedtauri-apps/tauri

cli.rs misidentifies target out directory for Cargo workspaces

<!-- BEFORE YOU FILE A NEW ISSUE--> <!--

  1. Please search open issues before duplicating a new one.
  2. Make sure you are using the latest version of everything including:
  • rustc
  • ALL relevant Tauri Libs
  1. You must attach the results of cargo tauri info or yarn tauri info to your issue.
  2. Make sure it is an issue with Tauri, and not something to do with your side of the stack.
  3. Consider starting a discussion. Speaking of which, have you looked there? Maybe your question has been answered.
  4. Remember to follow our community guidelines and be friendly.
  5. Is this an issue or a feature request? If the latter, please use the other template.

-->

Describe the bug

tauri build fails to detect that my src-tauri directory was part of a Cargo workspace. I realized the reason that function didn't work for me is because I use a glob to identify my workspace members, and Tauri CLI checks for exact matches. Directory structure that reproduces issue:

~/Documents/src-tauri-workspace/a-workspace (master)
$ tree -L 2
.
├── Cargo.lock
├── Cargo.toml
├── src
│   └── main.rs
├── src-tauri
│   ├── Cargo.toml
│   ├── icons
│   ├── rustfmt.toml
│   ├── src
│   └── tauri.conf.json
└── target
    ├── CACHEDIR.TAG
    ├── debug
    └── release

~/Documents/src-tauri-workspace/a-workspace (master)
$ cat Cargo.toml
[package]
name = "a-workspace"
version = "0.1.0"
edition = "2018"

[workspace]
members = ["src-tauri"]

[dependencies]

To Reproduce

  1. Clone https://github.com/kofigumbs/src-tauri-workspace
  2. cd a-workspace
  3. cargo tauri build
~/Documents/src-tauri-workspace/a-workspace (master)
$ cargo tauri build
   Compiling app v0.1.0 (/Users/kofi/Documents/src-tauri-workspace/a-workspace/src-tauri)
    Finished release [optimized] target(s) in 1m 20s
Error: failed to rename `/Users/kofi/Documents/src-tauri-workspace/a-workspace/src-tauri/target/release/a
pp` to `/Users/kofi/Documents/src-tauri-workspace/a-workspace/src-tauri/target/release/a-workspace`

Caused by:
    No such file or directory (os error 2)

Expected behavior

Tauri's target directory detection should always match that of cargo metadata:

~/Documents/src-tauri-workspace (master)
$ bash -c 'cd a-workspace && cargo metadata --format-version=1 | jq .target_directory'
"/Users/kofi/Documents/src-tauri-workspace/a-workspace/target"

~/Documents/src-tauri-workspace (master)
$ bash -c 'cd a-workspace/src-tauri && cargo metadata --format-version=1 | jq .target_directory'
"/Users/kofi/Documents/src-tauri-workspace/a-workspace/target"

Screenshots

N/A

Platform and Versions (required):

<!-- Use yarn tauri info or cargo tauri info command to get this information, and paste it here: -->

$ cargo tauri info

Operating System - Mac OS, version 11.5.2 X64

Node.js environment
  Node.js - 16.9.1
  @tauri-apps/cli - 1.0.0-beta.10

Global packages
  npm - 7.21.1
  yarn - Not installed

Rust environment
  rustc - 1.56.0-nightly
  cargo - 1.55.0-nightly

Additional context

I was pretty curious, since there seems to be workspace-specific code in interface/rust.rs#get_target_dir. I'm able to workaround this issue by explicitly setting CARGO_TARGET_DIR. My 2 cents is that Tauri should call cargo metadata directly, which would ensure that it uses the same resolution mechanism as Cargo itself. I think that approach would also resolve #2515, since you could also use the error message that Cargo uses for the same problem. My reproduction repo has a few more example project layouts and their cargo metadata output: https://github.com/kofigumbs/src-tauri-workspace.

Stack Trace

N/A

closed time in 8 hours

kofigumbs

PR merged tauri-apps/tauri

fix(cli.rs): fix workspace detection, fixes #2614, closes #2515

<!-- Please make sure to read the Pull Request Guidelines: https://github.com/tauri-apps/tauri/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

What kind of change does this PR introduce? (check at least one) <!-- If you are introducing a new binding, you must reference an issue where this binding has been proposed, discussed and approved by the maintainers. -->

  • [x] Bugfix
  • [ ] Feature
  • [ ] Docs
  • [ ] New Binding Issue #___
  • [ ] Code style update
  • [ ] Refactor
  • [ ] Build-related changes
  • [ ] Other, please describe:

Does this PR introduce a breaking change? (check one) <!-- If yes, please describe the impact and migration path for existing applications in an attached issue. Filing a PR with breaking changes that has not been discussed and approved by the maintainers in an issue will be immediately closed. -->

  • [ ] Yes. Issue #___
  • [ ] No

The PR fulfills these requirements:

  • [x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
  • [x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

  • [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

+55 -24

0 comment

5 changed files

lucasfernog

pr closed time in 8 hours

push eventtauri-apps/tauri

Lucas Nogueira

commit sha 904bdb22f777127dc6f7826f074aa65f084f8842

chore(deps): pin `wry`, update lock files

view details

Lucas Nogueira

commit sha d8fe9d6dc6dd0f2fe20c3a66bf2b5fe313d18588

feat(ci): run benchmarks on `next` branch

view details

Lucas Nogueira

commit sha 32a9451499bdd9cd0a41d068954d80a3986c6bc1

Merge branch 'next' into fix/workspace-detection

view details

push time in 16 hours

push eventtauri-apps/tauri

Lucas Nogueira

commit sha 904bdb22f777127dc6f7826f074aa65f084f8842

chore(deps): pin `wry`, update lock files

view details

Lucas Nogueira

commit sha d8fe9d6dc6dd0f2fe20c3a66bf2b5fe313d18588

feat(ci): run benchmarks on `next` branch

view details

Lucas Nogueira

commit sha b400de280e3bf61d55fb18c75df71b74505a5453

Merge branch 'next' into feat/cli.js-cjs

view details

push time in 16 hours

push eventtauri-apps/tauri

Lucas Nogueira

commit sha 904bdb22f777127dc6f7826f074aa65f084f8842

chore(deps): pin `wry`, update lock files

view details

Lucas Nogueira

commit sha d8fe9d6dc6dd0f2fe20c3a66bf2b5fe313d18588

feat(ci): run benchmarks on `next` branch

view details

Lucas Nogueira

commit sha f5028cc96131a9eed3267f549e4d00d52461ea74

Merge branch 'next' into fix/api-ts-output

view details

push time in 16 hours

push eventtauri-apps/tauri

Lucas Nogueira

commit sha 904bdb22f777127dc6f7826f074aa65f084f8842

chore(deps): pin `wry`, update lock files

view details

Lucas Nogueira

commit sha d8fe9d6dc6dd0f2fe20c3a66bf2b5fe313d18588

feat(ci): run benchmarks on `next` branch

view details

push time in 16 hours

push eventtauri-apps/tauri

Lucas Nogueira

commit sha dfb70abe70b1c17534ae165f3d2d1bc4d5447883

check if manifest exists

view details

push time in 17 hours

PR opened tauri-apps/vue-cli-plugin-tauri

feat: update to next @tauri-apps/cli release (hybrid ESM/CJS)

Works with https://github.com/tauri-apps/tauri/pull/2646

+3 -3

0 comment

2 changed files

pr created time in 17 hours

PR opened tauri-apps/tauri

feat(cli.js): add CommonJS dist files

<!-- Please make sure to read the Pull Request Guidelines: https://github.com/tauri-apps/tauri/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

What kind of change does this PR introduce? (check at least one) <!-- If you are introducing a new binding, you must reference an issue where this binding has been proposed, discussed and approved by the maintainers. -->

  • [ ] Bugfix
  • [x] Feature
  • [ ] Docs
  • [ ] New Binding Issue #___
  • [ ] Code style update
  • [ ] Refactor
  • [ ] Build-related changes
  • [ ] Other, please describe:

Does this PR introduce a breaking change? (check one) <!-- If yes, please describe the impact and migration path for existing applications in an attached issue. Filing a PR with breaking changes that has not been discussed and approved by the maintainers in an issue will be immediately closed. -->

  • [ ] Yes. Issue #___
  • [ ] No

The PR fulfills these requirements:

  • [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
  • [x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

  • [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

+22 -7

0 comment

2 changed files

pr created time in 17 hours

create barnchtauri-apps/vue-cli-plugin-tauri

branch : feat/update-next-cli

created branch time in 17 hours

create barnchtauri-apps/tauri

branch : feat/cli.js-cjs

created branch time in 17 hours

PR opened tauri-apps/tauri

fix(api): do not ship TS files, closes #2598

<!-- Please make sure to read the Pull Request Guidelines: https://github.com/tauri-apps/tauri/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

What kind of change does this PR introduce? (check at least one) <!-- If you are introducing a new binding, you must reference an issue where this binding has been proposed, discussed and approved by the maintainers. -->

  • [x] Bugfix
  • [ ] Feature
  • [ ] Docs
  • [ ] New Binding Issue #___
  • [ ] Code style update
  • [ ] Refactor
  • [ ] Build-related changes
  • [ ] Other, please describe:

Does this PR introduce a breaking change? (check one) <!-- If yes, please describe the impact and migration path for existing applications in an attached issue. Filing a PR with breaking changes that has not been discussed and approved by the maintainers in an issue will be immediately closed. -->

  • [ ] Yes. Issue #___
  • [ ] No

The PR fulfills these requirements:

  • [x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
  • [x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

  • [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

+6 -29

0 comment

4 changed files

pr created time in 17 hours

push eventtauri-apps/tauri

Lucas Nogueira

commit sha 65e9022de21d945a4b2d6684b398ce06e973fa03

change file

view details

push time in 17 hours

create barnchtauri-apps/tauri

branch : fix/api-ts-output

created branch time in 17 hours

PR opened tauri-apps/tauri

fix(cli.rs): fix workspace detection, fixes #2614, closes #2515

<!-- Please make sure to read the Pull Request Guidelines: https://github.com/tauri-apps/tauri/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

What kind of change does this PR introduce? (check at least one) <!-- If you are introducing a new binding, you must reference an issue where this binding has been proposed, discussed and approved by the maintainers. -->

  • [x] Bugfix
  • [ ] Feature
  • [ ] Docs
  • [ ] New Binding Issue #___
  • [ ] Code style update
  • [ ] Refactor
  • [ ] Build-related changes
  • [ ] Other, please describe:

Does this PR introduce a breaking change? (check one) <!-- If yes, please describe the impact and migration path for existing applications in an attached issue. Filing a PR with breaking changes that has not been discussed and approved by the maintainers in an issue will be immediately closed. -->

  • [ ] Yes. Issue #___
  • [ ] No

The PR fulfills these requirements:

  • [x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
  • [x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

  • [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

+53 -24

0 comment

5 changed files

pr created time in 17 hours

create barnchtauri-apps/tauri

branch : fix/workspace-detection

created branch time in 17 hours

issue closedtauri-apps/tauri

`--target` option for cli is not optional

<!-- BEFORE YOU FILE A NEW ISSUE--> <!--

  1. Please search open issues before duplicating a new one.
  2. Make sure you are using the latest version of everything including:
  • rustc
  • ALL relevant Tauri Libs
  1. You must attach the results of cargo tauri info or yarn tauri info to your issue.
  2. Make sure it is an issue with Tauri, and not something to do with your side of the stack.
  3. Consider starting a discussion. Speaking of which, have you looked there? Maybe your question has been answered.
  4. Remember to follow our community guidelines and be friendly.
  5. Is this an issue or a feature request? If the latter, please use the other template.

-->

Describe the bug

tauri build without the --target option fails when it tries to rename the generated binary to the specified product name because it assumes the wrong release directory (missing target path):

Error: failed to rename `<project-dir>/src-tauri/target/debug/<tauri cargo toml name>` to `<project-dir>/src-tauri/target/debug/<product name>`

Caused by:
    No such file or directory (os error 2)

When --target <target> is specified, it correctly finds the binary in ./src-tauri/target/<target>/debug

Platform and Versions (required):

<!-- Use yarn tauri info or cargo tauri info command to get this information, and paste it here: -->

Operating System - Mac OS, version 11.5.2 X64

Node.js environment
  Node.js - 16.9.1
  @tauri-apps/cli - 1.0.0-beta.10
  @tauri-apps/api - Not installed

Global packages
  npm - 7.21.1
  yarn - 1.22.11

Rust environment
  rustc - 1.54.0
  cargo - 1.54.0

App directory structure
/dist
/.cargo
/src-tauri
/assets
/src

App
  tauri.rs - 1.0.0-beta.8
  build-type - bundle
  CSP - default-src blob: data: filesystem: ws: wss: http: https: tauri: 'unsafe-eval' 'unsafe-inline' 'self' img-src: 'self'
  distDir - ../dist
  devPath - http://localhost:8080

Additional context

Add any other context about the problem here.

Stack Trace

<!-- add if applicable -->

Btw I ran the cli from the dev branch of a local git clone of the tauri repo but the same error also appears with the latest stable or beta releases.

closed time in 18 hours

jgeluk