Build status management

[guybedford]

Most package issues could be handled by having proper status pages for packages and package versions which display:

• The current package versions and builds, and when (and therefore which version) of the builder they were built with
• When there is no build for a given version, to display if this is due to a build error or a build timeout (by checking the _error page for the package, if it exists, its an error, otherwise its a pending build / timeout). Each build that has three possible statuses - "Built + Date Built", "Errored" and "Pending".
• Options for action on various build statuses. For example a pending build could have a "submit to build queue" button which calls the build queue API. An errored build could have a "Report and Request Rebuild" button. And a normal build could just have a "Report issue" button.

This could combine with a file + exports explorer for packages, including syntax highlighted source code with an "unminification" button when editing. In this way we provide insight into the CDN internals for debugging workflows, where these are currently lacking.

[matteeyah]

For me, the most important part would be just having insight into the status of a build for a package. It'd be great if I know if it's in progress, failed or waiting in queue. This is missing right now.

The part about debugging is cool, but I managed to get quite far with https://jspm.org/sandbox, https://generator.jspm.io/ and https://jspm.dev. I still haven't ran into a situation which I can't debug with the available tools.

This isn't to say that it wouldn't be a great addition, but I'd consider it as a quality of life improvement for developers, while the status information is something that's not accessible right now at all.