Package name and url route are conflicted

[shuuji3]

There is the settings package in npm.

When I open https://npmx.dev/settings, it navigates to the settings page, but when opening settings package from the search result, it enters the infinite loading loop.

We should use some prefix not allowed in the npm package name for special pages, for example, https://npmx.dev/_settings or something. According to the npm docs (https://docs.npmjs.com/cli/v11/configuring-npm/package-json/#name), package names cannot start with _ or ., so this will be a safe path while keeping the clean package url. Another option is to separate the namespace (for example, https://npmx.dev/p/settings).

Edit: see the following discussion and patak's comment.

npmjs.com uses the /package/ prefix like https://www.npmjs.com/package/settings.

[shuuji3]

related discussion: https://discord.com/channels/1464542801676206113/1464542802565140506/1466681838243414140

[mikouaji]

I'll add a fix for packages matching app routes being redirected to those pages later today. If its still needed depending how the discussion goes.

[patak-cat]

Surfacing this from the chat:

I think later on we will have the opportunity to use npmx for other cool things, like help with funding, events and communities discovery (and more features?), useful tooling:

npmx.dev/sponsor/{name}
npmx.dev/collective/{name}
npmx.dev/event/{name}
npmx.dev/conference/{name}
npmx.dev/tool/{name} <-- e18e like experiences that doesn't fit in the UI
npmx.dev/stats/{name} <-- global stats for the ecosystem
npmx.dev/licence/{name} <-- license info
npmx.dev/report/{name}

I think it is worth having the URLs clean too and not have always a /_/{route}/{name} in there just because of the cleaner package URL (that again, it works too for almost every package, just redirects to /package/{name} in npmjs.com

[lino-levan]

Update from discord, we more or less settled on:

npmx.dev/package/{name}
npmx.dev/package-docs/{name}
npmx.dev/package-code/{name}
npmx.dev/package-?/{name}
npmx.dev/sponsor/{name}
npmx.dev/collective/{name}
npmx.dev/event/{name}
npmx.dev/conference/{name}
npmx.dev/tool/{name} <-- e18e like experiences that doesn't fit in the UI
npmx.dev/stats/{name} <-- global stats for the ecosystem
npmx.dev/licence/{name} <-- license info
npmx.dev/report/{name}

[shamilkotta]

I would like to work on this

[mikouaji]

@shamilkotta Hey, I'm already working on larger changes to routing and it will solve this and some other similar issues

[mikouaji]

Fixed with #674

[shuuji3]

Thanks!