feat: use nuxtimg instead of standard img tag

[niklhut]

Summary by CodeRabbit

• Refactor
  • Replaced standard image elements in book listing and add-book screens with optimized image components, improving image handling and load performance without changing appearance or behavior.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Replaced standard HTML img elements with NuxtImg components in two files. Source bindings, classes, alt text, and loading behavior were preserved; no logic or exported API changes were introduced.

Changes

Cohort / File(s)	Summary
Image Component Replacement app/components/BookCard.vue, app/pages/library/add.vue	Replaced HTML img tags with self-closing NuxtImg components. Preserved src bindings, classes, alt text, and loading attributes (lazy/eager). No functional or API changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 I hopped in to swap tags with care,
NuxtImg now frames each cover fair.
Classes and sources stayed the same,
A tiny tweak—yet not for fame.
Hooray for small, neat code repair! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: replacing standard HTML img tags with NuxtImg components across the codebase.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

---

📜 Recent review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7ae614d and 0512e1c.

📒 Files selected for processing (1)

• app/components/BookCard.vue

🔇 Additional comments (1)

app/components/BookCard.vue (1)

102-108: LGTM! NuxtImg replacement is correct.

The migration from <img> to <NuxtImg> preserves all necessary attributes (src, alt, class, loading) and is consistent with the non-selectable mode usage above. Since your nuxt.config.ts is configured with image: { provider: 'none' }, NuxtImg will safely pass through the dynamic API routes (/api/blob/...) without modification, which is the right approach when your blob images are already optimized.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@app/components/BookCard.vue`:
- Around line 102-109: The inline comment above the image element is stale: it
says "Use img directly for blob URLs" but the template now uses the NuxtImg
component (see the NuxtImg element with v-if="coverUrl", :src="coverUrl",
:alt="title"). Update or remove that comment so it reflects the current
implementation (either change it to note that NuxtImg is used for blob/WebP URLs
or delete the comment entirely) to avoid confusion.

📜 Review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 88dd33e and 7ae614d.

📒 Files selected for processing (2)

• app/components/BookCard.vue
• app/pages/library/add.vue

🔇 Additional comments (2)

app/components/BookCard.vue (1)

56-62: LGTM!

The NuxtImg component with lazy loading is appropriate for card grids. The internal blob URL path will work correctly without additional configuration.

app/pages/library/add.vue (1)

180-186: No action needed regarding external domain configuration.

The image configuration in nuxt.config.ts is set to provider: 'none', which means NuxtImg operates as a simple pass-through component without image optimization. External URLs like lookupResult.coverUrl from OpenLibrary will load directly without requiring domain configuration.

Likely an incorrect or invalid review comment.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}