fix: filter search cannot be typed

[rzzf]

The search input in Filters cannot accept any input.
https://npmx.dev/org/vue

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Feb 11, 2026 9:02am

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored	Preview	Feb 11, 2026 9:02am
npmx-lunaria	Ignored		Feb 11, 2026 9:02am

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes refactor the filter text input binding in the Filter Panel component. A new computed property filterText was introduced to establish two-way data binding with the filter text value. The component binding was updated from a unidirectional :value assignment to use v-model with the new computed property. The explicit handleTextInput event handler was removed in favour of the computed property's setter to emit text update events. This simplifies the data flow for managing the filter text input within the InputBase component.

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description check	✅ Passed	The pull request description directly addresses the changeset, identifying a specific bug (search input cannot accept input) with a reproducible URL and explaining the fix applied.

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

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

---

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

[codecov]

Codecov Report

❌ Patch coverage is 25.00000% with 3 lines in your changes missing coverage. Please review.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
app/components/Filter/Panel.vue	25.00%	2 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!

[danielroe]

I think we should use a defineModel('text') instead

[rzzf]

This property comes from props.filters.text, so is defineModel('text') unnecessary?
If so, ListToolbar.vue would also need to be updated accordingly.

Referenced from

npmx.dev/app/components/Package/ListControls.vue

Lines 22 to 25 in 9aae078

	const filterValue = computed({
	get: () => props.filter,
	set: value => emit('update:filter', value),
	})

[danielroe]

ahh, I see.

yes, this is awkward prop drilling we need to fix at some point but not in this PR