From 746dc2af3ac3c527bb28be833165bee0d2a2f0e2 Mon Sep 17 00:00:00 2001 From: Bowden Kelly Date: Tue, 9 May 2017 14:01:33 -0700 Subject: [PATCH] update README --- README.md | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/README.md b/README.md index dae7b67..b3dc50f 100644 --- a/README.md +++ b/README.md @@ -345,20 +345,6 @@ This all happens in memory when you run the tests, so there are no output `.js` Writing tests for web apps has entire books dedicated to it and best practices are strongly influenced by personal style, so I'm deliberately avoiding discussing how or when to write tests in this guide. However, if prescriptive guidance on testing is something that you're interested in, [let me know](TODO-survey-link), I'll do some homework and get back to you. -## Using ES6 Modules - -## Adding types - -## Configuring your VS Code environment - -### Project settings - -### Extensions - -#### TSLint - -#### Spellcheck - ## TSLint TSLint is a code linter which mainly helps catch minor code quality and style issues. TSLint is very similar to ESLint or JSLint but is built with TypeScript in mind.