tauri-apps / tauri-apps/tauri-docs

[request] Reintroduce v1 “Reducing App Size” guidance in v2 docs

Open
#3,414 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

discuss enhancement
Dominant language
MDX
Stars
1.1k
Forks
887
Avg merge
2d 8h
Merged PRs (30d)
48

Description

Question you want answered

Is the JavaScript minification and all the other advice from the v1 “Reducing App Size” page still valid for Tauri v2? If so, can we re-add or merge that content into the v2 Concept: Size guide?

Where did you look for an answer?

I browsed the v2 docs under Concept → Size but didn't see any frontend-bundle optimization tips (JavaScript minification, etc.). I also searched this repo for some keywords from the original v1 article.

Page URL

https://v2.tauri.app/concept/size/

Additional context

The v1 guide at https://v1.tauri.app/v1/guides/building/app-size/ walks through steps such as: Minify Javascript, Optimize Dependencies, Optimize Images, etc. In v2, that content is missing. It'd help newcomers if we either re-add those steps if they are still valid / required in Tauri v2.

Are you willing to work on this yourself?
  • I want to work on this myself

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the v2 Concept: Size guide and compare it with the v1 “Reducing App Size” guide, especially the sections on JavaScript minification, dependency optimization, and image optimization. Check which advice remains valid for Tauri v2, then re-add or merge the applicable guidance into the v2 page. Done means newcomers can find the relevant frontend-bundle size advice in the v2 guide.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.