fix: Build errors — remove unused useRef, add @tiptap/suggestion dep,…

[devohmycode]

… bump tauri version to 0.6.1

Summary by CodeRabbit

Release Notes

• Chores
  • Updated Tauri framework to version 0.6.1
  • Added text suggestion library dependency
  • Cleaned up unused imports

[qodo-code-review]

Review Summary by Qodo

Fix build errors and bump Tauri to 0.6.1

🐞 Bug fix ✨ Enhancement

Walkthroughs

Description

• Add missing @tiptap/suggestion dependency to resolve build errors
• Remove unused useRef import from BookmarkPanel component
• Bump Tauri version from 0.5.0 to 0.6.1
• Update pnpm lock file with new dependency resolution

Diagram

flowchart LR
  A["Build Issues"] --> B["Add @tiptap/suggestion"]
  A --> C["Remove unused useRef"]
  A --> D["Bump Tauri 0.5.0→0.6.1"]
  B --> E["Updated Dependencies"]
  C --> E
  D --> E

Loading

File Changes

1. package.json Dependencies +1/-0

Add missing @tiptap/suggestion dependency

• Added @tiptap/suggestion package at version ^3.20.0
• Maintains consistency with other @tiptap extension versions

package.json

---

2. pnpm-lock.yaml Dependencies +3/-0

Update lock file with suggestion package

• Added lock entry for @tiptap/suggestion@3.20.0
• Includes dependency resolution for @tiptap/core and @tiptap/pm

pnpm-lock.yaml

---

3. src-tauri/tauri.conf.json ⚙️ Configuration changes +1/-1

Bump Tauri version to 0.6.1

• Bumped application version from 0.5.0 to 0.6.1

src-tauri/tauri.conf.json

---

View more (1)

4. src/components/BookmarkPanel.tsx 🐞 Bug fix +1/-1

Remove unused useRef import

• Removed unused useRef import from React
• Keeps necessary imports: useState, useEffect, useCallback

src/components/BookmarkPanel.tsx

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. package-lock not updated 🐞 Bug ⛯ Reliability

Description

package.json adds @tiptap/suggestion, but package-lock.json and README are still oriented around
npm, making the repo inconsistent for npm users (npm ci may fail or npm install will rewrite the
lockfile). CI uses pnpm, so contributors will get different dependency resolution depending on the
tool they follow.

Code

package.json[40]

+    "@tiptap/suggestion": "^3.20.0",

Evidence

The PR adds @tiptap/suggestion to package.json, but package-lock.json’s root dependency list does
not include it, while the README still instructs using npm. Meanwhile CI installs with pnpm,
indicating the repo currently supports multiple package managers without keeping them in sync.

package.json[34-46]
package-lock.json[6-48]
README.md[195-223]
.github/workflows/build.yml[44-54]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The repo currently mixes pnpm (CI + pnpm-lock.yaml) and npm (README + package-lock.json). This PR adds a direct dependency (`@tiptap/suggestion`) but does not reconcile the npm lockfile + docs, which can cause `npm ci` failures or uncommitted lockfile changes for contributors following the README.

## Issue Context
- CI installs dependencies with `pnpm install`.
- README instructs `npm install` / `npm run dev`.
- `package.json` now includes `@tiptap/suggestion`, but `package-lock.json` root deps list does not.

## Fix Focus Areas
- package.json[34-46]
- package-lock.json[6-48]
- README.md[195-223]
- .github/workflows/build.yml[44-54]

## Expected fix approaches (pick one)
1) **pnpm-first**: remove `package-lock.json`, update README to use pnpm, optionally add `"packageManager": "pnpm@<version>"`.
2) **dual-support**: regenerate and commit `package-lock.json` so it matches `package.json`, and clarify in README which lockfile/package manager is supported.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Version bump incomplete 🐞 Bug ✓ Correctness

Description

The PR bumps the Tauri app version to 0.6.1, but the UI still displays a hardcoded older version and
other manifests remain on different version numbers, causing user-facing and release/debugging
confusion. This is especially relevant because the PR explicitly changes the app version but does
not update other version surfaces.

Code

src-tauri/tauri.conf.json[4]

+  "version": "0.6.1",

Evidence

The Tauri config version was updated to 0.6.1 by this PR, but the About panel still shows a
hardcoded v0.4.0, and the JS/Rust manifests also show different versions. That means the app can
present contradictory version information depending on where you look.

src-tauri/tauri.conf.json[1-8]
src/components/SourcePanel.tsx[1068-1078]
src-tauri/Cargo.toml[1-4]
package.json[1-5]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The PR updates the Tauri app version to 0.6.1, but other places still show different versions (UI About panel hardcoded to v0.4.0; Cargo/package.json versions differ). This results in inconsistent version reporting for users and during releases/debugging.

## Issue Context
- The version bump is explicitly part of this PR.
- The About panel is user-facing and currently hardcodes an older version.
- There are multiple version sources in the repo that are not synchronized.

## Fix Focus Areas
- src-tauri/tauri.conf.json[1-8]
- src/components/SourcePanel.tsx[1068-1078]
- src-tauri/Cargo.toml[1-4]
- package.json[1-5]

## Suggested implementation direction
- Replace the hardcoded About version with a dynamic value:
 - Prefer `@tauri-apps/api/app` `getVersion()` when running under Tauri.
 - Provide a dev fallback (e.g., `import.meta.env.VITE_APP_VERSION` injected at build time) so `vite` dev in a browser doesn’t break.
- Decide a single source of truth and align other version fields to it (e.g., set package.json + Cargo.toml to 0.6.1, and keep tauri.conf.json consistent).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0524d48 and 546fb7d.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (3)

• package.json
• src-tauri/tauri.conf.json
• src/components/BookmarkPanel.tsx

---

📝 Walkthrough

Walkthrough

Dependencies and configuration updates have been applied. The Tiptap suggestion library was added to project dependencies, the Tauri configuration version was bumped to 0.6.1, and an unused React hook import was removed from a component.

Changes

Cohort / File(s)	Summary
Dependency & Configuration Updates package.json, src-tauri/tauri.conf.json	Added @tiptap/suggestion dependency (v^3.20.0) and updated Tauri configuration version from 0.5.0 to 0.6.1.
Import Cleanup src/components/BookmarkPanel.tsx	Removed unused useRef hook from React imports; component retains useState, useEffect, and useCallback.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A suggestion blooms in Tauri's garden fair,
With versions climbing up the version stair,
Imports swept clean with a careful paw,
Dependencies aligned without a flaw!

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 0.6.1

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[qodo-code-review]

1. Package-lock not updated 🐞 Bug ⛯ Reliability

package.json adds @tiptap/suggestion, but package-lock.json and README are still oriented around
npm, making the repo inconsistent for npm users (npm ci may fail or npm install will rewrite the
lockfile). CI uses pnpm, so contributors will get different dependency resolution depending on the
tool they follow.

Agent Prompt

## Issue description
The repo currently mixes pnpm (CI + pnpm-lock.yaml) and npm (README + package-lock.json). This PR adds a direct dependency (`@tiptap/suggestion`) but does not reconcile the npm lockfile + docs, which can cause `npm ci` failures or uncommitted lockfile changes for contributors following the README.

## Issue Context
- CI installs dependencies with `pnpm install`.
- README instructs `npm install` / `npm run dev`.
- `package.json` now includes `@tiptap/suggestion`, but `package-lock.json` root deps list does not.

## Fix Focus Areas
- package.json[34-46]
- package-lock.json[6-48]
- README.md[195-223]
- .github/workflows/build.yml[44-54]

## Expected fix approaches (pick one)
1) **pnpm-first**: remove `package-lock.json`, update README to use pnpm, optionally add `"packageManager": "pnpm@<version>"`.
2) **dual-support**: regenerate and commit `package-lock.json` so it matches `package.json`, and clarify in README which lockfile/package manager is supported.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools