The rest can be summed up in a little Q&A.
- What does JSPkg do?
It hosts the downloadable
- So it competes with Github?
For now, you can import from any publicly-accessible git repository.
- Why do projects require a package.json file?
And as it turns out, a spec for such a structured meta-file already exists as part of the CommonJS movement and has been adopted by projects such as NodeJS. That file is called
- Is there a Command Line Interface (CLI)?
Not yet. The command line has been the goal from the beginning. Ideally, we want *every* JS developer to be able to use this, so we wanted to make sure we have all the bases covered. The game plan is to start with the lowest common denominator: a slick web interface that absolutely everyone can use.
One of the issues with creating a command line utility is that it usually has to be built in some higher-level language or framework, which then has to be installed on the user's computer. Projects like Rubygems have the advantage of knowing that the user will have ruby installed. NPM knows the user will have Node.js. But for front-end JS packages, we really can't be sure they'll have anything installed. It'd be nice to avoid making front-end developers install something only tangentially related. It would be really cool to have a command line utility just written in bash to do commands like such as
jspkg install easytabsand string together
All that being said, we have designed a nice restful API into the site from the very beginning, and will soon be adding documentation.
Furthermore, we've made JSPkg.com a CommonJS package registry, so any CLI tools that can communicate with a registry should be able to plug into JSPkg as a repo. For a list of such repos, check out our CLI Projects info page.
- Is JSPkg for jQuery Plugins?
- Does JSPkg provide a CDN, so I don't have to download the files?
Not yet, but the JSPkg CDN is on its way.
- What does JSPkg's technology stack look like?
JSPkg is built atop Rails 3.1 and jQuery, hosted on Heroku. We will soon be open-sourcing a lot of the code-base as soon as we get it off the ground. It uses many open-source projects, including jQuery, Twitter Bootstrap, and a number of RubyGems.
It may have been more poetic to build this site in Node.js or some other JS-based framework. But we wanted to get the job done and Rails is what we know best!