The Jig framework sets up a decent front-end development environment quickly. It sets you up to use:
You need to have
npm installed to manage the modules,
and run the tests.
If you're an experienced front-end web developer and just want to use Jig to get running fast, follow the instructions below. If you're not an experienced front-end web developer read the Jig wiki after you run the instructions below:
git clone my-new-projectcd my-new-projectnpm install
In the near future, you should be able to do:
mkdir my-new-projectcd my-new-projectnpm install jig-framework
Both of the above are "local installs", meaning everything goes in your project directory and nothing is available globally. The advantage of this approach is that it's easier to work on multiple projects that need different versions of packages. The disadvantage is that you have to type long command names sometimes, and you have to wait for the packages to install for each new project.
test. That's the Mocha default
public. That's where the test server looks for files by default
If you're running
it will also run the tests after any file changes.
The languages and frameworks supported by Jig require translation (transpiling) to work from a browser. To automatically transpile your files every time you change or add a file:
To run a test web server, installed locally:
By default, the server listens on port 8080,
so point your browser to
It gets files from
If you installed the Jig framework globally:
sudo apt-add-repository ppa:chris-lea/node.jssudo apt-get updatesudo apt-get install nodejs
If you're setting up Node on a Debian-derived distribution, you need to create a link to make your system work like all the documents you'll see:
sudo ln -s /usr/bin/nodejs /usr/bin/node