User account works in org page

[bluwy]

Describe the bug

If my npm username is bluwy, currently npmx supports https://npmx.dev/org/bluwy, which is a bit confusing as I'm not an org. https://npmx.dev/~bluwy works of course, but it's missing some packages I maintain like publint and vitefu.

With npmjs, if you navigate to https://www.npmjs.com/org/bluwy, it'll redirect you to https://www.npmjs.com/~bluwy. The packages shown is the same as https://npmx.dev/org/bluwy.

So from what I can tell, the data at https://npmx.dev/org/bluwy is correct and should also be shown at https://npmx.dev/~bluwy, in which case, maybe https://npmx.dev/org/bluwy should not be supported? (redirect to /~bluwy like npmjs)

Additional context

Related, https://npmx.dev/search?q=bluwy is suggesting me as an org rather than a user, which seems intentional:

npmx.dev/app/composables/npm/useSearch.ts

Lines 123 to 130 in 0d0707f

	const newSuggestions: SearchSuggestion[] = []
	if (isOrg) {
	newSuggestions.push({ type: 'org', name: lowerName, exists: true })
	}
	if (isUser && !isOrg) {
	newSuggestions.push({ type: 'user', name: lowerName, exists: true })
	}
	suggestions.value = newSuggestions

Logs

[maxchang3]

I think redirecting to /~bluwy like npmjs would be the better choice.

---

On a related note:

https://npmx.dev/~bluwy works of course, but it's missing some packages I maintain

Related to #1882, #1888, the current Algolia search query does have issues.

the data at https://npmx.dev/org/bluwy is correct

It seems the organization package list is retrieved directly from the npm registry, rather than using Algolia, as the username page does.

npmx.dev/server/api/registry/org/[org]/packages.get.ts

Lines 32 to 34 in 8976969

	const data = await $fetch<Record<string, string>>(
	`${NPM_REGISTRY}/-/org/${encodeURIComponent(org)}/package`,
	)