You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 10, 2020. It is now read-only.
Currently we use symbolic links to make sure both new/old names work on CDN, but it'll not work on the website as there is no record in public/packages.min.json.
To implement this feature, we need to add a function in cdnjs/cdnjs's build/packages.json.js to add record of libraries with symbolic links, and implement 302/301 redirect route in webServer.js app
Feel free to open a new issue for it, as I was removed from the organization without any discussion and respect, just like some other members(I know it's not by you and you're not the one who's in charge for that), I'm now closing ancient issues I'm not working on so that I don't need to receive unnecessary notifications, thanks.
As mentioned here and here, please use the unsubscribe button in this issue if you no longer wish to receive notifications for it. However, please leave this issue open as it is still needed.
Currently we use symbolic links to make sure both new/old names work on CDN, but it'll not work on the website as there is no record in
public/packages.min.json
.To implement this feature, we need to add a function in cdnjs/cdnjs's
build/packages.json.js
to add record of libraries with symbolic links, and implement 302/301 redirect route inwebServer.js
appcc cdnjs/cdnjs#4627
The text was updated successfully, but these errors were encountered: