Unpublished packages should not return a 404

[lowlighter]

The API should be able to differentiate between a missing package and an empty package.

If you curl the API on a created package but that has no release yet, it shouldn't return a 404:

404 - Not Found

But rather a JSON similar to this one, just with no versions and maybe latest set to null

{
  "scope": "scope",
  "name": "package",
  "latest": null,
  "versions": {}
}

Also on a related note, using the version badge with an unreleased package should also be updated accordingly to inform the package exist but isn't released yet

[lucacasonato]

I can not reproduce this: https://api.jsr.io/scopes/luca/packages/test.

// 20240712101348
// https://api.jsr.io/scopes/luca/packages/test

{
  "scope": "luca",
  "name": "test",
  "description": "",
  "githubRepository": null,
  "runtimeCompat": {
    
  },
  "updatedAt": "2024-02-28T15:25:34.812982Z",
  "createdAt": "2024-02-28T15:25:34.812982Z",
  "versionCount": 0,
  "score": null,
  "latestVersion": null,
  "whenFeatured": null
}

[lowlighter]

It's when you curl the meta.json

curl https://jsr.io/@luca/test/meta.json
404 - Not Found

curl https://jsr.io/@luca/pi/meta.json
{
  "scope": "luca",
  "name": "pi",
  "versions": {
    "1.2.0": {},
    "1.0.0": {},
    "1.1.0": {}
  }
}

As for the badge maybe i should open another issue, but this is definitely happening

[lucacasonato]

Ah ok - this is currently intentional for the meta.json. It is only created once the first version is published - what is the use case?

[lowlighter]

Just getting package metadata

It's just the https://jsr.io/docs/api#package-metadata doesn't precise that the package should have been published with at least one version

Package metadata

Package metadata refers to the information about a package as a whole, such as the package scope, name and versions.
Package metadata is served as JSON at the following URL:

https://jsr.io/@scope/package-name/meta.json

[...]

This allows a tool to discover the available versions of a package and perform semantic versioning resolution to determine the best version to use.

The endpoint you gave is basically what I was looking for, but maybe it's worth to update the doc, or at least return a JSON with an error field because it''s causing a media type mismatch between text/json