Hi Tim, I'm getting "No 'Access-Control-Allow-Origin' header...." on my lit package browser (http://develephant.github.io/lit-browser/#/). I'm guessing CORS is needed?
I'm hoping to take if off Github sites and put it on a regular box, and then work on an updated version, especially with the new info you've added. Cheers On Tuesday, April 28, 2015 at 3:25:33 PM UTC-5, Tim Caswell wrote: > > Many of you have asked for some sort of search functionality in the public > lit database so you can see what luvit/lit modules are already out there. > > I'm making progress towards this being as nice as what's at npm.org > <http://www.google.com/url?q=http%3A%2F%2Fnpm.org&sa=D&sntz=1&usg=AFQjCNFVH9fTDz9r8ms4wGJVv65Tcwc9Hw> > . > > If you're running the latest lit client, then new packages you publish > will have extra metadata stored in the git tag making it accessible to my > server to find. > > Also today I deployed a new lit server to lit.luvit.io that has a new > search command in the API. > > Check out the following sample queries to see what the results look like > (I recommend having the jsonview extension in your browser) > > https://lit.luvit.io/search/msgpack > https://lit.luvit.io/search/coro > https://lit.luvit.io/search/weblit > https://lit.luvit.io/search/luvit > https://lit.luvit.io/search/virgo > > Currently it only matches against package names or author names and > includes both in the results. If it is a package it pulls out some > metadata, especially in newer packages since the lit client update. > > Let me know what you think, and anyone with web-dev experience is welcome > to try their hand at a HTML+JS frontend. I can host it at luvit.io if > you wish or add CORS headers to the REST calls so your client can be hosted > anywhere. > > -Tim Caswell > -- You received this message because you are subscribed to the Google Groups "luvit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
