Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I've found these package managers for in-browser javascript:</p> <ul> <li><a href="https://github.com/kriszyp/cpm" rel="nofollow noreferrer">CPM</a> (CommonJS package manager), focused on Dojo packages, with an archive at <a href="http://packages.dojofoundation.org/" rel="nofollow noreferrer">http://packages.dojofoundation.org/</a> (about 60 packages). CPM augments the CommonJS format with a <a href="http://wiki.commonjs.org/wiki/Packages/Mappings/C" rel="nofollow noreferrer">mappings field</a> to describe how modules from dependent packages can be require()d</li> <li>Caolan's <a href="http://jamjs.org/" rel="nofollow noreferrer">Jam</a>, whose archive is at <a href="http://jamjs.org/packages/" rel="nofollow noreferrer">http://jamjs.org/packages/</a>. Here is the <a href="http://jamjs.org/docs#Developing_packages" rel="nofollow noreferrer">Jam packaging guide</a>.</li> <li><a href="http://enderjs.com/" rel="nofollow noreferrer">Ender</a> piggybacks on <a href="http://npmjs.org/" rel="nofollow noreferrer">npm</a> for package management, and provides a client that looks like AMD (I'm not sure about AMD compatibility, which according to a bug report is left up to each package). Here are the Ender <a href="http://enderjs.com/#publishing" rel="nofollow noreferrer">packaging docs</a>. Here are <a href="https://www.npmjs.com/browse/keyword/ender" rel="nofollow noreferrer">packages with the ender keyword</a>. Ender doesn't focus on packaging existing libraries, though its Jeesh starter pack is a modular, mostly-compatible replacement for jQuery.</li> </ul> <p>Most of these can publish in the <a href="https://github.com/amdjs/amdjs-api/wiki/AMD" rel="nofollow noreferrer">AMD format</a> for browser loaders, and can be loaded by <a href="http://requirejs.org/" rel="nofollow noreferrer">RequireJS</a>. They also tend to use the <a href="http://wiki.commonjs.org/wiki/Packages" rel="nofollow noreferrer">CommonJS package format</a> (also used by npm) for their package.json metadata.</p> <p>I also found <a href="http://readthedocs.org/docs/xstatic/" rel="nofollow noreferrer">XStatic</a>, which seems to be a less-active version of fanstatic, and like fanstatic wraps the libraries in Python packages. It has the same limitation (versions tend to lag), but writing a wrapper package seems simple enough that I can bake my own updates. </p> <p>BPM and fanstatic are aware of non-js assets and can merge or minify CSS.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload