To start with JavaScript, we are going to setup everything we need.

The first exercise will be to get everything up and running.

The setup will be described for Linux based operating systems (Using apt-get for packages)

If you are not a Vim user, we suggest you to install Sublime Text 3

It is highly configurable text editor.

For the difference between an IDE and a text editor, we suggest you to watch the following video: https://www.youtube.com/watch?v=qLDU8ugpO9Y (It's in Bulgarian)

This is a good start to equip your Vim for JavaScript use - http://oli.me.uk/2013/06/29/equipping-vim-for-javascript/

In the beginning, we are going to interpret our JavaScript programs using NodeJS.

To quote the official website:

Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications.

Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

We are not going to build server applications - just run JavaScript programs to test input and output of functions.

• To install NodeJS on Ubuntu, follow this guide - https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager#ubuntu-mint-elementary-os
• For different OS you can check the Wiki page - https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager

In order to check if everything is ok, run:

$ node --version
v0.10.28

This will be our sanity check tool. JSHint check the JavaScript file for bad practices or JavaScript pitfalls.

We will integrate it with Sublime, but first, we need to install it:

$ npm install jshint -g

You may need super user to do this.

Check the docs here - http://www.jshint.com/docs/

This will help our interpretator to enforce more strict rules on the code we are writing.

JavaScript is one of those languages that needs strict rules in order to avoid the so-called "bad parts".

You can read more about it:

• http://stackoverflow.com/questions/1335851/what-does-use-strict-do-in-javascript-and-what-is-the-reasoning-behind-it
• http://ejohn.org/blog/ecmascript-5-strict-mode-json-and-more/

We suggest some default settings for coding in JavaScript.

Open the file run_this.js in Sublime and after this, in the menu, find Preferences -> Settings - More -> Syntax Specific - User

This should open a file called JavaScript.sublime-settings. Here you can write your custom settings for the editor.

We recommend the following defaults as a base:

{
    "draw_white_space": "all",
    "rulers": [80],
    "tab_size": 2,
    "translate_tabs_to_spaces": true,
    "trim_trailing_white_space_on_save": true,
    "ensure_newline_at_eof_on_save": true,
    // Set to true to automatically save files when switching to a different file
    // or application
    "save_on_focus_lost": true,
}

For base, we are going to use SublimeCodeIntel and JSHint Gutter

If you have fresh Sublime installed, first, you need to get the Package Control plugin - https://sublime.wbond.net/installation

After this, in Sublime, press ctrl + shift + p and type Install Package

In the following order, install:

• SublimeCodeIntel
• JSHint Guttter

In Sublime, open Preferences -> Package Settings -> JSHint Gutter -> Set Plugin Options

You can change the following options:

{
  // Automatically lint on edit (Sublime Text 3 only).
  "lint_on_edit": true,
  ...
  // Automatically lint when a file is saved.
  "lint_on_save": true,
  ...
}

Open run_this.js and press : ctrl + shift + j You should see some "Console is not defined" errors.

Now open Preferences -> Package Settings -> JSHint Gutter -> Set Linting Preferences and add console to globals:

{
    "globals": {
        "console" : true
  }
}

Now run_this.js should be linted withour any problems ( ctrl + shift + j )

In the week0 folder, there is a file called run_this.js

Open a terminal window and try to execute it:

$ node run_this.js

You should get some output from it :)

Now, open the file called run_this.html in a browser (We recommend Chrome).

Open the browser console and navigate to the console output.

You should see the same result as from the NodeJS.

If you have the required setup, you can move to:

• tic-tac-toe folder, where there is a game to finish. It is a console-based tic-tac-toe. README.md there will give you more instructions.
• problems folder, where there are simple coding problems to be solved using JavaScript (With NodeJS). Again, README.md there for more instructions.