Merge pull request #135 from code-dot-org/webpack-closure

Run closure compiler under webpack

.gitignore

@@ -1,3 +1,4 @@
 node_modules/
+dist/
 .DS_Store
 /.idea

README.md

@@ -35,7 +35,7 @@ Major additions and changes in this fork:
 ```
 cd blockly
 npm install
-./deploy.sh
+npm run build
 ```
 
 ## Usage
@@ -59,11 +59,11 @@ cd {code-dot-org repo directory}/apps
 npm link @code-dot-org/blockly
 ```
 
-Apps will now reference your local blockly repository rather than the npm package. If you then make local changes to your repo, you can simply rebuild blockly (via `./deploy`) and then apps (via `npm run build`) to communicate those changes to apps.
+Apps will now reference your local blockly repository rather than the npm package. If you then make local changes to your repo, you can simply rebuild blockly (via `npm run build` in this repo) and then apps (via `npm run build` in code-dot-org/apps) to communicate those changes to apps.
 
 ### Publishing changes
 
-To publish a new version to npm switch to the master branch, use `npm login` to sign in as an account with access to the `@code-dot-org` scope, then `npm version [major|minor|patch]` for the appropriate version bump.  This will do the following:
+To publish a new version to npm switch to the master branch, use `npm login` to sign in as an account with access to the `@code-dot-org` scope, then `npm version [major|minor|patch|premajor|preminor|prepatch]` for the appropriate version bump.  This will do the following:
 
 * Run linting and tests to verify your local repo.
 * Rebuild the release package.

blocks/functional_procedures.js

@@ -26,6 +26,7 @@
 goog.provide('Blockly.Blocks.functionalProcedures');
 
 goog.require('Blockly.Blocks');
+goog.require('Blockly.Blocks.procedures');
 
 /**
  * Definition block for a custom functional block