The impetus for this is, users are reporting [1][2][3][4] that they can't find plugins, and I don't think they know of a search alternative.
In the near term, I think we should tweet how to search for plugins using npmjs.com [1] https://twitter.com/edeortuzar/status/843310576101146625 [2] https://twitter.com/kumakumadev/status/843149557127155712 [3] https://twitter.com/quangv/status/842925319254360064 [4] https://twitter.com/skumarSDsoft/status/842677001433497600 On Sun, Mar 19, 2017 at 1:19 PM, Shazron <shaz...@apache.org> wrote: > ### PROBLEM > > Plugin search is broken. > > ### DESCRIPTION > > Page: > http://cordova.apache.org/plugins/ > > JIRA: > https://issues.apache.org/jira/browse/CB-12579 > > > Q: How does the plugin search work? > > A: > Page Source: http://cordova.apache.org/plugins > and the source (this specific line): http://svn.apache.org/ > viewvc/cordova/site/public/plugins/index.html?view=markup#l117 > > which is added from here: > https://github.com/apache/cordova-docs/blob/master/www/plugins/index.html > > which is generated from this React code: > https://github.com/apache/cordova-docs/blob/a3589ce66336821f2fd714a1115125 > cfcfa9fd1b/www/static/plugins/app.js > > Nothing shows up as errors in the Web Inspector, so it is hard to track > down. > > ### MY PROPOSAL > > The era of needing npmsearch.com to populate this page is over. We could > just redirect users to npmjs.com and add the "ecosystem:cordova" token > (i.e https://www.npmjs.com/search?q=ecosystem%3Acordova) > > The alternative is to use npm's Registry API: https://github.com/npm/ > registry/commits/master/docs/REGISTRY-API.md > > The API was only documented earlier this year, if not we would have used > it. > >
