Remove Grunt

.gitignore

@@ -4,6 +4,7 @@
 .baseDir.js
 .baseDir.ts
 yarn.lock
+.nyc_output
 yarn-error.log
 
 /src/typings/typescript/typescript.js

.travis.yml

@@ -17,5 +17,5 @@ before_install: >
   fi
 
 script:
- - npm test
+ - npm run build_and_test
  - npm run lint

.vscode/tasks.json

@@ -6,15 +6,15 @@
     {
       "label": "build",
       "type": "shell",
-      "command": "npm run grunt -- default",
+      "command": "npm run build",
       "problemMatcher": [
         "$tsc"
       ]
     },
     {
       "label": "build_and_test",
       "type": "shell",
-      "command": "npm run grunt -- build_and_test",
+      "command": "npm run build_and_test",
       "problemMatcher": [
         "$tsc"
       ]

CONTRIBUTING.md

@@ -97,13 +97,13 @@ You can automatically fix some style problems by running `npm run lint -- --fix`
 
 #### Building
 
-To compile the TypeDoc source, run `npm run grunt`. This will start the TypeScript compiler and output the compiled JavaScript to the `dist` folder. If you want to build and test in one step, run `npm run build`.
+To compile the TypeDoc source, run `npm run build`. This will start the TypeScript compiler and output the compiled JavaScript to the `dist` folder. If you want to build and test in one step, run `npm run build_and_test`.
 
 #### Testing
 
 TypeDoc includes an extensive set of tests that describe its output. To validate any changes you have made, build the project and then run `npm test`. Alternatively, to rebuild with your changes and then immediately test, run `npm run build`.
 
-If you have changed the TypeDoc output, it will cause tests to fail. Once you have validated that the introduced changes were intended, run `npm run grunt -- update-specs` to update the spec files for the new output.
+If you have changed the TypeDoc output, it will cause tests to fail. Once you have validated that the introduced changes were intended, run `node scripts/rebuild_specs` to update the spec files for the new output.
 
 ## Pull Requests
 

UPDATING.md

@@ -1,49 +1,32 @@
 
 ## Updating
-TypeDoc makes use of internal API methods from the TypeScript compiler - as such you will need
-to recompile it for each and every different TypeScript compiler release. If your project doesn't
-rely on features from the latest TypeScript compiler, you may be able to get away with using
-version of TypeDoc which doesn't target it.
+TypeDoc uses internal TypeScript compiler APIs. Since internal APIs can be changed by a minor
+release, TypeDoc must target exact TypeScript compiler versions. If your project is using a newer
+version of TypeScript than TypeDoc, but does not rely on features from the latest version, you
+may be able to get away with using a version of TypeDoc that targets a lower TypeScript version.
 
-If, however, you need the latest version and one hasn't yet been published then these are the steps
+If you need the latest version and one hasn't yet been published then these are the steps
 you should follow to build your own.
 
 ```bash
 # Checkout a copy of TypeDoc if you don't have one already
-git clone https://github.com/TypeStrong/typedoc typedoc
+git clone https://github.com/TypeStrong/typedoc
 cd typedoc
 
 # Change the version of TypeScript used by the project
 editor package.json
 
-npm install -g grunt-cli # install grunt's CLI globally if you don't have it
 npm install # install TypeDoc's dependencies
 
-# Checkout the version of TypeScript you are targetting
-git clone https://github.com/Microsoft/TypeScript typescript
-cd typescript
-git checkout v1.8.10 # checkout the correct version (as set in package.json)
-npm install -g jake # install the jake build tool globally if you don't have it
-npm install # install TypeScript's build dependencies
-jake local # build TypeScript
-cd ../
-
-# Setup TypeDoc for your TypeScript version
-grunt ts:typescript # compile the internal-API typescript definition files
-grunt string-replace:typescript # format the internal-API typescript files
-
 # Build and run the automated TypeDoc tests
-grunt build_and_test 
-
-# Do a visual inspection to make sure that modules were generated correctly
-ls test/render/specs/modules
+npm run build_and_test
 ```
 
 Once this has been done, you should have a functional version of TypeDoc for
-your version of TypeScript. If you're so inclined, please open a Pull Request
-with your updated project so that others may benefit from the update.
+your version of TypeScript. Please open a Pull Request with your updated project
+so that others may benefit from the update.
 
-To make use of your version of TypeDoc in a project, point your `package.json`
+To use your version of TypeDoc in a project, point your `package.json`
 file at it using your GitHub project path.
 
 ```json
@@ -52,4 +35,4 @@ file at it using your GitHub project path.
         "typedoc": "mygithubuser/typedoc#v1.8.10"
     }
 }
-```
+```