No results matched when filtering by semver

[rzzf]

Describe the bug

https://npmx.dev/package/vue

The following filter conditions return no results:

• 3.5.1
• =3.5.1
• >=3.5.0 <3.5.8
• ~3.4.0
• 3.4.x

Additional context

No response

Logs

[serhalp]

🤔 That is very interesting. I wonder what's going on here. Pagination quirk?

[maxchang3]

Currently, filtering only considers known (already loaded) versions here:

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

Lines 117 to 135 in 524919e

	const semverFilter = ref('')
	// Collect all known versions: initial props + dynamically loaded ones
	const allKnownVersions = computed(() => {
	const versions = new Set(Object.keys(props.versions))
	for (const versionList of tagVersions.value.values()) {
	for (const v of versionList) {
	versions.add(v.version)
	}
	}
	for (const group of otherMajorGroups.value) {
	for (const v of group.versions) {
	versions.add(v.version)
	}
	}
	return [...versions]
	})
	const filteredVersionSet = computed(() =>
	filterVersions(allKnownVersions.value, semverFilter.value),
	)

And a tag row is shown only if its primary version matches the filter:

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

Lines 198 to 201 in 524919e

	const rows = isFilterActive.value
	? rowsMaybeFilteredForDeprecation.filter(row =>
	filteredVersionSet.value.has(row.primaryVersion.version),
	)

All versions may need to be loaded when applying a filter. Also, row visibility could depend on whether any version in the row matches.