[Bug]: error decoder page links standalone packages to non-existent URLs

[kgryte]

Description

Encountered an error when attempting to navigate away from the error decoder page https://stdlib.io/docs/api/latest/error/decoder/1V13P by clicking on the standalone package link at the bottom.

Currently, the link uses the standalone package name, but it should use the mono-repo package name instead, so that users can actually view the API documentation for the package.

Related Issues

n/a

Questions

Linking to the mono-repo package name is not actually straightforward. In particular, an error message from a standalone package may

1. originate from a package which is no longer in the main repo (e.g., the package was deprecated, being either moved or removed entirely).
2. be linked to a particular version of the main @stdlib/stdlib project. This is due to the fact that an error message is associated with a particular state of the @stdlib/stdlib project and the version in which that error message applies may not be "latest", but some prior version of the project.

Currently, all error decoder URLs route to latest, but this is not "correct" due to the aforementioned reasons. I think, ideally, when a user attempts to navigate to an error decoder URL (e.g., https://stdlib.io/e/1V13P), the server needs to determine which version of the API docs to return. It may be latest, but it could also be some earlier version (e.g., v0.3).

Demo

https://stdlib.io/e/1V13P

Reproduction

• navigate to https://stdlib.io/e/1V13P
• attempt to click on the link at the bottom of the error decoder overlay

Expected Results

Should navigate to https://stdlib.io/docs/api/latest/@stdlib/utils/key-by-right

Actual Results

Navigates to https://stdlib.io/docs/api/latest/@stdlib/utils-key-by-right

Environments

N/A

Browser Version

No response

Node.js / npm Version

No response

Platform

No response

Checklist

• Read and understood the Code of Conduct.
• Searched for existing issues and pull requests.

[kgryte]

As an addendum, at some point, we have also discussed have a version of the docs (possibly via a settings toggle, or a dedicated mount path) which caters to standalone package usage, similar to what we have in the standalone repositories.

In which case, instead of the mono-repo package path, we could link to the standalone package path, but then this gets tricky when considering the fact that standalone packages are independently versioned.

Alternatively, for standalone packages, we could simply link out to the respective standalone repository, rather than attempt to navigate to a page within the API documentation.