<div class="quote"><i>TOR wrote:
<p>Great question! We may have a library of components of some sort in the future.
</p><p>However, knowing the fierce independence of some of our communities, and drawing on my Wikipedia experience with Wikimedia Commons, I’m gonna say it’s probably not quite the silver bullet it appears to be. ;)
</p><p>We’re probably going to wait and see how dev wiki evolves and is used, now that it is a de facto global repository of JS scripts -- and there’s actually a way to sort of easily import them to your wiki, plus an incentive to use the global scripts to not have to go through JS review as often.
</p><p>So if you care about this idea, head over to
dev.wikia.com and help out over there -- or better yet, convince your wiki friends to start using global JS scripts from dev. We'll be watching and taking notes. :)
</p>
</i></div>
<p>Another user and I have populated a whole page full of Lua modules (
w:c:dev:luamods), and I crafted extensive guides to help create lua modules. We are even using some global modules from there in this wikia. One idea is to provide a highly customizable bare-bones framework that users can import and change at will.
</p><p>I think that lua scripts are quite good because there's no need to convince anyone that they work. They can see loads of unit tests (see
w:c:dev:links/testcases) that can help with "sane" testing. The only thing that is missing is some kind of LUA review system trusted users, e.g. code-editors review. Something similar to the JS review so that users don't get served problematic modules altered by ignorant users . Alternatively high use scripts can simply be protected or or added as libraries like mw.ustring, e.g. mw.quote.
</p><p>There a quite a few javascripts I've created and submitted, but stopped this until we have a proper JS review in place. Maybe one day we'll eventually have a more vibrant coder community there.
</p>