Repository navigation
Include package deprecation information in API response #14236
Description
GET https://api.cdnjs.com/libraries/datatables.net?fields=versions returns
{
"versions": [
"1.10.12",
"1.10.13",
"1.10.14",
"1.10.15",
"1.10.16",
"1.10.18",
"1.10.19",
"1.10.20",
"1.10.21",
"1.10.22",
"1.10.23",
"1.10.24",
"1.10.25",
"1.11.0",
"1.11.1",
"1.11.2",
"1.11.3",
"1.11.4",
"1.11.5",
"1.12.0",
"1.12.1",
"1.13.0",
"1.13.1",
"1.13.10",
"1.13.11",
"1.13.2",
"1.13.3",
"1.13.4",
"1.13.5",
"1.13.6",
"1.13.7",
"1.13.8",
"2.0.0",
"2.0.1",
"2.0.2",
"2.0.3",
"2.1.1"
]
}One would naively assume from this response that 2.1.1 is the latest version of the package, but in reality it is a deprecated version (https://www.npmjs.com/package/datatables.net/v/2.1.1). It would be nice if the API either offered an option to exclude deprecated versions when making the request or included deprecation metadata in the response.
This issue was originally raised here: aspnet/LibraryManager#724.
Reacted by CePur and Michael Yang
Activity
MattIPv4 commentedon Mar 25, 2024
cc cdnjs/packages#926 cdnjs/packages#1307 cdnjs/packages#1289
Dxuian commentedon Aug 23, 2024
im new to OS is this still open?
MattIPv4 commentedon Aug 23, 2024
Yup, this issue is still open. If you're planning to work on it, I would recommend writing up your intended approach first, so that folks familiar with cdnjs' systems can provide feedback before you spend time on any implementation.