I am currently trying to understand better how packages are requested from bundles, from the proxy, and eventually from the CTAN repo. In that process, I noticed some discrepancies that should probably be resolved at some point.
The following API endpoints are currently implemented in packages/ctan-proxy.ts:
/api/stats/api/pkg//api/deps//api/fetch/
However, the following requests are made in src/ctan.js:
/api/texlive//api/fetch//api/ctan-pkg/
The only overlap is /api/fetch/.
The easy fix is to make /api/pkg/ and /api/ctan-pkg/ match (if they are intended to match, which I believe they are).
The bigger issue is that I cannot find an implementation of /api/texlive/. It is unclear to me whether it is ever needed, or whether it would bring a significant performance improvement over /api/fetch/.
I am currently trying to understand better how packages are requested from bundles, from the proxy, and eventually from the CTAN repo. In that process, I noticed some discrepancies that should probably be resolved at some point.
The following API endpoints are currently implemented in
packages/ctan-proxy.ts:/api/stats/api/pkg//api/deps//api/fetch/However, the following requests are made in
src/ctan.js:/api/texlive//api/fetch//api/ctan-pkg/The only overlap is
/api/fetch/.The easy fix is to make
/api/pkg/and/api/ctan-pkg/match (if they are intended to match, which I believe they are).The bigger issue is that I cannot find an implementation of
/api/texlive/. It is unclear to me whether it is ever needed, or whether it would bring a significant performance improvement over/api/fetch/.