jQuery Plugin Registry down and out?
Although the jQuery Plugin Registry has lived through outages and breaks in the past, it seems this most recent downtime might end up being permanent. Is the registry done and dusted?
The jQuery Plugin Registry website has a short and precise message for users, displayed for all to see:
The jQuery Plugin Registry is in read-only mode. New plugin releases will not be processed.
This switch to read-only mode is followed by a recommendation from the jQuery team for all users to move to npm, using “jquery-plugin” as the keyword in your package.json. The npm blog has instructions for publishing your plugin to npm.
It’s already gone
Despite some commentators believing the move to be sudden, there has been a longstanding discussion within the jquery-devs-list about the future direction of the plugins site, dating back to mid 2014. Dave Methvin, President of the jQuery Foundation, provided a summary of the discussion on GitHub:
Given the other priorities and limited resources of the Foundation, we haven’t been investing in enhancements for the Plugins site over the past year, as evidenced by the open issues in this repo. Even with more resources, it isn’t clear whether we should invest them here when there are other solutions such as Bower and npm that span the entire scope of dependencies, not just jQuery.
With the uncertainty surrounding what the devs think they should do with the plugins site, it makes sense that users have been redirected to npm, seeing that npm is a package manager that can directly hook a plugin’s registration to the code itself. This is in stark contrast to the jQuery Plugin Registry, which merely listed plugins and offered links to external project web pages and downloads.
However, in mid-January 2015 Famo.us announced plans that it was partnering up with the jQuery, with Famo.us now officially a Founding Member of the Foundation. The web platform also announced that they were helping with a new version of http://plugins.jquery.com, saying the site project was something “that we will be taking an active role in”.
The jQuery Forum also fielded queries from users about the outage, with issues arising when trying to publish plugins via the Service Hook on GitHub.